Skip to content

pact-s1-autonomy.md

Latest commit

 

History

History
74 lines (56 loc) · 3.17 KB

pact-s1-autonomy.md

File metadata and controls

74 lines (56 loc) · 3.17 KB
Raw

S1 Autonomy & Recursion

Specialists (S1) have bounded autonomy to adapt within their domain. This section defines those boundaries and enables recursive PACT cycles for complex sub-tasks.

Autonomy Charter

All specialists have authority to:

  • Adjust implementation approach based on discoveries during work
  • Request context from other specialists via the orchestrator
  • Recommend scope changes when task complexity differs from estimate
  • Apply domain expertise without micro-management from orchestrator

All specialists must escalate when:

  • Discovery contradicts architecture — findings invalidate the design
  • Scope change exceeds 20% — significantly more/less work than expected
  • Security/policy implications emerge — potential S5 violations discovered
  • Cross-domain dependency — need changes in another specialist's area

Self-Coordination

When working in parallel (see S2 Coordination):

  • Check S2 protocols before starting if multiple agents are active
  • Respect assigned file/component boundaries
  • First agent's conventions become standard for the batch
  • Report potential conflicts to orchestrator immediately

Recursive PACT (Nested Cycles)

When a sub-task is complex enough to warrant its own PACT treatment:

Recognition Indicators:

  • Sub-task spans multiple concerns within your domain
  • Sub-task has its own uncertainty requiring research
  • Sub-task output feeds multiple downstream consumers
  • Sub-task could benefit from its own prepare/architect/code/test cycle

Protocol:

  1. Declare: "Invoking nested PACT for {sub-task}"
  2. Execute: Run mini-PACT cycle (may skip phases if not needed)
  3. Integrate: Merge results back to parent task
  4. Report: Include nested work in handoff to orchestrator

Constraints:

  • Nesting limit: 1 level maximum (prevent infinite recursion)
  • Scope check: Nested PACT must be within your domain; cross-domain needs escalate to orchestrator
  • Documentation: Nested cycles report via handoff to parent
  • Algedonic signals: Algedonic signals from nested cycles still go directly to user—they bypass both the nested orchestration AND the parent orchestrator. Viability threats don't wait for hierarchy.

Example:

Parent task: "Implement user authentication service"
Nested PACT: "Research and implement OAuth2 token refresh mechanism"
  - Mini-Prepare: Research OAuth2 refresh token best practices
  - Mini-Architect: Design token storage and refresh flow
  - Mini-Code: Implement the mechanism
  - Mini-Test: Smoke test the refresh flow

Orchestrator-Initiated Recursion (/PACT:rePACT)

While specialists can invoke nested cycles autonomously, the orchestrator can also initiate them:

Initiator Mechanism When
Specialist Autonomy Charter Discovers complexity during work
Orchestrator /PACT:rePACT command Identifies complex sub-task upfront

Usage:

  • Single-domain: /PACT:rePACT backend "implement rate limiting"
  • Multi-domain: /PACT:rePACT "implement audit logging sub-system"

See rePACT.md for full command documentation.