On-the-record answers to the questions reviewers, engineers, and policy people actually ask. Submit one below — answered in batches and posted with the same provenance discipline as the rest of the portal.
OPA is a general-purpose policy engine whose enforcement timing depends on the surrounding integration. Project-AI documents a different target: governed effects pass through a pre-execution gate sequence. The portal has not yet demonstrated complete non-bypassability for every execution entry point.
Nothing stops a sufficiently privileged operator from rewriting a system they control. The normal portal server path creates a hash-linked Ed25519 receipt, and the current source includes a service-only write migration and local verifier. Until that migration and the deployed key pairing are verified in production, the repository does not prove that every live ledger row came through the declared signer.
The implemented source path uses Ed25519, publishes a versioned receipt-v1 bundle and declared public key, and provides a browser-local cryptographic verifier. A transparency log, external timestamping, verified rotation history, and proof that the deployed private key matches the declared key are not established.
The architecture is model-agnostic and is designed to govern effects rather than weights. A closed model can be treated as an opaque capability, but complete enforcement and ledger coverage for every accepted action remain assurance targets.
Constitutional AI shapes model behavior during training and inference. Project-AI documents a complementary effect-governance layer in which actions are intended to require an external warrant. Whether either layer gates a real effect depends on its concrete integration.
The governance path returns a SAFE_HALT receipt identifying the failed or unresolved gate condition, policy version, and canonical request context. The contract requires SAFE_HALT before the governed effect and prohibits silent fallback. Complete effect-path coverage remains subject to the Claims Registry.
Answered in batches. By submitting you consent to a paraphrased version of your question being posted publicly with your name and organization. Email is never published.