J94/bit-vector-tensor-control-policy

1# Session Bootstrap2 3Clean product one-liner: this is the reusable onboarding packet for a fresh agent session.4 5Why: one file should tell the next session where it is, what governs it, and what payloads it may emit.6 7## Start Here8 9- Read [/Users/jobs/Desktop/bit-vector-tensor-control-policy/api/session_bootstrap.json](/Users/jobs/Desktop/bit-vector-tensor-control-policy/api/session_bootstrap.json) first for the machine-readable context.10- Then run `./bin/bvtctl context` to refresh the live view.11- Use `./bin/bvtctl "<question>"` for reasoning or `./bin/bvtctl ask "<question>" [manifest]` for bounded execution.12 13## Current Position14 15- Entry slice: conversational_api16- Default profile: operator17- Lineage view: operator_lineage18- Role: single front-door operator over the whole system19 20## System Lineage21 22- conversational_api23- product_runtime24- graph_kernel25- control_benchmarks26- orchestrator_ux27 28## Governance29 30- enter through the conversational API before opening lower-level surfaces31- read policy and lineage before proposing execution32- use manifests for bounded action and receipts for proof33- treat graph state and receipts as higher authority than prose summaries34- show the user one coherent system view, not subsystem fragments35 36## Payload Shapes37 38- Turn request: `POST /turn` with auto-hydrated `system_context`, `policy_context`, and `lineage_context`.39- Turn response: lane, control vector, tensor surface, execution gate, decision brief, and `system_context`.40- Work manifest: bounded actions plus receipt-backed execution.41 42## Stable Commands43 44- `./bin/bvtctl context`45- `./bin/bvtctl bootstrap-context`46- `./bin/bvtctl "summarise the current runtime"`47- `./bin/bvtctl ask "run the demo manifest" runtime/examples/demo_manifest.json`48