docs: define bounded AI execution OS charter

[NoctilumeDev]

Purpose

Evolve FlowKernel's public research contract from a lifecycle-aware AI resource-scheduling kernel into a planned C-first AI Execution OS research program, while preserving the original scheduling question and keeping implementation status honest.

This PR adds one constitutional document and aligns the existing vision, C-first contract, hypotheses, roadmap, evidence policy, threat model, prior-art map, contribution workflow, and repository gate around bounded authority, deterministic enforcement, fault containment, provenance, recovery, and external acceptance.

Evidence state

• Planned
• Designed

No implementation has started or been validated.

Verification

• node scripts/verify-repository.mjs — PASS (24 text files, 15 Markdown files)
• git diff --check HEAD^ HEAD — PASS
• fixed-coordinate source documents used by conceptual-origin.md were resolved locally to Git blobs
• no-context stranger review — original six counterexamples closed; final schema regression PASS; STOP verdict

Not run: kernel build, boot, Docker, workload benchmark, security deep scan, multi-principal governance, clean-machine R0 recovery. This is a docs-only design-contract change.

Safety and scope

• Original lifecycle/resource-scheduling history remains explicit.
• Policy/model artifacts do not become capability-holding Principals.
• Authorization, execution, AcceptanceVerdict, evidence, and EpistemicStatus remain separate.
• C is an enforcement boundary, not a correctness proof.
• Append-only provenance is not described as tamper-proof.
• Single-maintainer GitHub governance is not described as validated multi-party governance.
• No kernel modules, fake releases, product components, or implementation claims were added.