api/session_bootstrap.md

Session Bootstrap

Clean product one-liner: this is the reusable onboarding packet for a fresh agent session.

Why: one file should tell the next session where it is, what governs it, and what payloads it may emit.

Start Here

• Read /Users/jobs/Desktop/bit-vector-tensor-control-policy/api/session_bootstrap.json first for the machine-readable context.
• Then run ./bin/bvtctl context to refresh the live view.
• Use ./bin/bvtctl "<question>" for reasoning or ./bin/bvtctl ask "<question>" [manifest] for bounded execution.

Current Position

• Entry slice: conversational_api
• Default profile: operator
• Lineage view: operator_lineage
• Role: single front-door operator over the whole system

System Lineage

• conversational_api
• product_runtime
• graph_kernel
• control_benchmarks
• orchestrator_ux

Governance

• enter through the conversational API before opening lower-level surfaces
• read policy and lineage before proposing execution
• use manifests for bounded action and receipts for proof
• treat graph state and receipts as higher authority than prose summaries
• show the user one coherent system view, not subsystem fragments

Payload Shapes

• Turn request: POST /turn with auto-hydrated system_context, policy_context, and lineage_context.
• Turn response: lane, control vector, tensor surface, execution gate, decision brief, and system_context.
• Work manifest: bounded actions plus receipt-backed execution.

Stable Commands

• ./bin/bvtctl context
• ./bin/bvtctl bootstrap-context
• ./bin/bvtctl "summarise the current runtime"
• ./bin/bvtctl ask "run the demo manifest" runtime/examples/demo_manifest.json