
governance
Protocols for reading Architect specifications and filing implementation reports.
by FrostadEng|Open Source
Governance Protocol
Instruction: Read Active Spec
Trigger: When starting a new task.
- Locate: Find the latest file in
.project_governance/specs/(excludearchive/). - Summary: Output the 3-bullet summary of the objective.
- Library Check (Context7 Integration):
- Scan: Does the Spec mention external libraries (e.g.,
pandas,scipy,pint)? - Action: If YES, use the
context7tool to fetch the latest documentation for that specific module. - Goal: Verify that the methods requested in the Spec actually exist in the current version.
- Scan: Does the Spec mention external libraries (e.g.,
- Internal Check:
- "Does this spec require me to use
mech_core?" (Yes/No).
- "Does this spec require me to use
- Confirm: Ask user to proceed.
Instruction: File Report
Trigger: When task is done.
- Write: Create
.project_governance/reports/report_[Date]_[Feature].md. - Include:
- Status (Pass/Fail)
- Files Modified
- External Deps: "Verified
scipysyntax via Context7."
- Map Logic:
- Check: Did this implementation add new directories?
- Action: If YES, execute "Update Map" (cartographer).
- Handoff: "Report filed. Run
/audit."