secondme canon ops v0

role: current process plan

use this page when you need to understand how the company should update the constitution.

core idea

the constitution is a compiled artifact.

raw inputs do not write doctrine directly.
they move through:

1. raw capture
2. atom extraction
3. section impact routing
4. section inbox review
5. patch proposal
6. human approval
7. canon update

operating assumption

inputs arrive noisy and unlabeled:

• customer interviews
• investor conversations
• telegram chats
• brainstorms
• operator notes
• external research

the routing layer, not the source author, decides which doctrine sections they affect.

agent roles

• ingest agent
• reads raw artifacts
• extracts atoms
• routing agent
• maps atoms to section impact
• section agents
• review inboxes for specific constitution sections
• editor agent
• assembles patch proposals
• review agent
• checks overreach and contradiction
• orchestrator
• controls cadence, thresholds, and review state

rhythms

event-driven

• after every interview, investor call, telegram digest, research memo, or pilot log
• extract atoms and route section impact

nightly

• refresh section inboxes
• compute daily doctrine delta
• flag sections whose thresholds may be crossed

weekly

• generate section proposals
• create patch pack for human approval

monthly

• archive stale cards
• kill hanging bets
• review slow doctrine sections

card system

minimum card types:

• raw artifact
• atom
• section impact
• proposal
• review note

status

done

• canonical doctrine exists
• local canon ops pack exists in docs/canon/
• section roles are clear
• process model is defined
• machine-readable section registry exists
• card schemas exist
• file scaffold exists for cards/, inbox/, and reviews/
• protected public constitution exists in the strategy hub

next

• build nightly cron
• build weekly patch-pack generation
• define human approval workflow
• choose whether section inboxes are stored on disk or compiled as views
• define freshness and contradiction scoring

not started

• automated raw artifact discovery
• atom extraction jobs
• section impact routing jobs
• proposal generation jobs
• inbox views
• stale evidence decay

design rules

• raw chat never updates doctrine directly
• agents may propose doctrine changes, not approve them
• update sections by impact, not by source type
• each section has its own cadence and threshold
• keep observed, inferred, recommended, and already started separate

local operating entry

start here if you are improving company meta-process:

1. docs/canon/status.md
2. docs/canon/runbook.md
3. docs/canon/sections.yaml
4. docs/project-constitution.md