Cory Control Plane

Govern requests with Cory before code, approvals, and KM diverge.

The current baseline includes project and repo foundations, execution surfaces, and the realignment toward a Cory-first workflow where interpretation comes before manual form entry or runner execution.

Target workflow spine

raw intakeinterpretationdraft reviewapprovalexecutionevidencekm

Ready for review

04

Requests or execution handoffs waiting for human review

Blocked

02

Workflows waiting on clarification, approval, or policy input

Active workflows

03

Interpreted requests currently moving through governed state

Governance preview

Current surfaces, aligned toward interpreted request workflows

Step 1

raw intake

Audit-friendly state reserved for explicit transitions and human governance.

current direction
Step 2

interpretation

Audit-friendly state reserved for explicit transitions and human governance.

current direction
Step 3

draft review

Audit-friendly state reserved for explicit transitions and human governance.

current direction
Step 4

approval

Audit-friendly state reserved for explicit transitions and human governance.

current direction
Step 5

execution

Audit-friendly state reserved for explicit transitions and human governance.

current direction
Step 6

evidence

Audit-friendly state reserved for explicit transitions and human governance.

current direction
Step 7

km

Audit-friendly state reserved for explicit transitions and human governance.

current direction