fb9d91e510
Add adaptive, evidence-driven architecture upgrade: decision-loop orchestrator, action catalog, evidence-state handoffs, process quality, stop conditions
...
- Orchestrator: linear flow replaced by adaptive decision loop
(UNDERSTAND→ESTIMATE→LOAD CONTEXT→CHOOSE ACTION→EXECUTE→VERIFY→RE-PLAN/STOP→LEARN)
- New sections: Task Complexity Estimation (ESTIMATE→EXECUTE→EXPAND),
Action Catalog with 24 tool-card actions, Evidence-First State and Handoff
Discipline (9-field state records, state separation, long-horizon persistence),
Process Quality anti-patterns, Cost and Token Awareness, Stop Conditions,
adaptive planning + failure recovery (7 failure types), lightweight quality gates
- All 13 agents preserved; 12 subagents gain role-adapted Evidence & Handoffs
sections (evidence product, stop, escalation) after Repository Intelligence
- Repository Intelligence Bootstrap extended with Knowledge Lifecycle rules;
.opencode structure unchanged (knowledge/state dirs intentionally not added)
- New docs: AGENT_ARCHITECTURE.md (full architecture incl. simple/complex
execution traces, ownership table, weaknesses) and EVALUATION_SCENARIOS.md
(12 runtime scenarios + scoring rubric)
- New test: scripts/test-agent-architecture.sh (16 structural checks)
- Validation: 16/16 architecture tests PASS, 11/11 bootstrap tests PASS,
install 13/13 + permission verifier PASS, live config synced byte-identical
2026-09-07 12:53:30 -04:00
c1f5f939ad
Add Repository Intelligence Bootstrap: repo-bootstrap.sh, all 13 agents updated, docs, tests
...
- scripts/repo-bootstrap.sh: generic idempotent bootstrap tool (status/bootstrap/refresh)
- creates .opencode/ with repo-context, architecture, build-and-test, conventions, deployment skills
- relevance-based skill generation (only creates what the repo actually has)
- staleness detection via .bootstrap-meta (key=value, SHA-256 fingerprints)
- marker-based manual protection (never overwrites unmarked files)
- accepts --root flag for explicit repo targeting
- scripts/test-repo-bootstrap.sh: 11 tests covering all 10 acceptance criteria
- creation, idempotency, manual preservation, relevance detection
- orchestrator/agent structural checks, staleness, genericness
- install.sh workflow compatibility, malformed handling
- agents/orchestrator.md: first-class Repository Intelligence Bootstrap stage
- 10-step workflow, ownership rules table, staleness signals
- consumption rules, backward compatibility, fallback procedure
- All 12 subagent files: role-adapted Repository Intelligence section
- architect: owns architecture skill
- builder/tester: own build-and-test skill (shared)
- explorer: owns repo-context skill
- maintainer: owns conventions skill + audits .opencode/
- reviewer: validates consistency (consumer/reporter)
- designer/detective/philosopher/toolsmith/workflow-architect/writer: consume-only
- docs/REPOSITORY_INTELLIGENCE.md: full architecture documentation
- README.md: updated layout, bootstrap usage, requirements
- 13/13 agents installed, permission-engine verifier PASS
2026-09-07 12:10:25 -04:00
36caa15959
Unify all agent write permissions; reconcile read-only prompt text
...
All 13 agents now use a uniform writable permission model
(edit: allow, bash: allow) so every agent can persist its deliverables
and artifacts instead of being sandbox-denied on project writes.
Orchestrator retains task: allow for dispatching.
Reconciled the three agents (explorer, detective, reviewer) that still
carried a 'Hard Read-Only Boundary' and read-only role-fence wording
which contradicted the new permissions and caused self-censoring:
rewritten as role fences (investigate/diagnose/review != implement/fix),
keeping the report IS the deliverable boundary and UNVERIFIED handoff.
Builder/tester/maintainer were already writable and unchanged.
2026-09-07 07:30:00 -04:00
0ec44a4ee4
Add workflow-architect agent; raise team to 13 agents
...
- New workflow-architect subagent: FSM-first modeling with explicit
model-selection strategy (statechart, DAG, decision tree, BPMN, Petri,
saga, etc.), gap detection, failure/recovery as first-class, output
spec format, and role fence vs Architect/Orchestrator.
- Orchestrator: add Workflow Architect to Specialist Map, roster,
dispatch rule, workflow-modeling classification, handoff decision,
final rules, and explicit dynamic agent selection (not a fixed
pipeline).
- Installer EXPECTED_COUNT 12->13; docs/README/PROMPT_INSTALL updated;
AgentsReport/workflow-architect seeded.
2026-09-07 01:57:59 -04:00
66564a1eaa
Adopt canonical permission standard v1 + installer verification gate
2026-08-24 15:51:09 -04:00
f697675f7a
Export 12-agent team + installer
2026-08-23 07:56:08 -04:00
Your Name