You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Objective\n\nDefine and land the long-term Harness tool-governance contract before expanding the current activation implementation.\n\n## Scope\n\n- establish a canonical glossary before the design\n- separate catalog availability, durable activation intent, policy admission, and per-call effective ToolPlan\n- define additive activation, exact replacement, explicit deactivation/suppression, reset, dynamic withdrawal and republish semantics\n- define owner/generation/provenance and publication-versus-activation boundaries\n- define observability and an acceptance/state-transition matrix\n- preserve Product ownership of defaults, policy, prompts, and presentation\n- identify staged implementation slices without implementing P1 behavior in this design change\n\n## Context\n\nP0 in #516 preserves deferred requested names when collaboration tools are activated additively. The remaining governance design must prevent later work from conflating requested intent with currently available or effective tools, including the dynamic-tool republish resurrection case.\n\n## Deliverable\n\nA reviewed Harness architecture document and glossary, with three independent design reviews incorporated.
Objective\n\nDefine and land the long-term Harness tool-governance contract before expanding the current activation implementation.\n\n## Scope\n\n- establish a canonical glossary before the design\n- separate catalog availability, durable activation intent, policy admission, and per-call effective ToolPlan\n- define additive activation, exact replacement, explicit deactivation/suppression, reset, dynamic withdrawal and republish semantics\n- define owner/generation/provenance and publication-versus-activation boundaries\n- define observability and an acceptance/state-transition matrix\n- preserve Product ownership of defaults, policy, prompts, and presentation\n- identify staged implementation slices without implementing P1 behavior in this design change\n\n## Context\n\nP0 in #516 preserves deferred requested names when collaboration tools are activated additively. The remaining governance design must prevent later work from conflating requested intent with currently available or effective tools, including the dynamic-tool republish resurrection case.\n\n## Deliverable\n\nA reviewed Harness architecture document and glossary, with three independent design reviews incorporated.