The OsaTechGPT stack is intentionally split. A proof runtime should not also pretend to be the memory layer, authorization layer, cloud control plane and operational sandbox. Each system owns a narrower responsibility and exposes evidence at its boundary.
MISSION / POLICY
↓
OSA EXECUTION FORCE — authority + capability gate
↓
HYDRA — sandboxed operational runtime
↓
NEUROSA — persistent cognitive state
↓
OSA CLOUD WORKSPACE — source/build/runtime evidence
APR sits across execution paths as a proof layer:
MISSION → EXECUTE → CHECK → PROOF → VERIFY
| System | Canonical role | Public evidence |
|---|---|---|
| Agent Proof Runtime | Execution evidence and independent verification. | Public repository, validation docs, external Devpost surface. |
| Hydra Hermes Lab | Sandboxed agent runtime, routing, permissions, duty cycle and ledger. | Public repository with sanitized runtime and control-plane evidence. |
| NeurOSA Human Brain | Programmable persistent cognitive state, memory workspace and ledger. | Public R&D repository with tests and architecture lock. |
| OSA Execution Force | Authority, policy binding, capability gates and downstream execution control. | Public repository with V3 authority proof; production readiness is not claimed. |
| OSA Cloud Workspace | Source SHA → build → image → revision → verification control plane. | Public repository and validation semantics; runtime freshness must be verified separately. |
| Money Graph | Opportunity intelligence layer. | No dedicated public proof surface; no separate SEO claim page is created. |
A system can be real without being publicly verified. OsaTechGPT therefore separates public source, mechanical validation, live runtime evidence and private/internal capability.
If a layer has no public proof, the site says so. It is not upgraded to “production ready” because a marketing page exists.
APRExecution evidence and independent verification.
Hydra Hermes LabSandboxed operational runtime and control.
NeurOSAPersistent programmable cognitive state.
OSA Execution ForceAuthority, capability gates and downstream execution control.
OSA Cloud WorkspaceSource-to-runtime cloud evidence and operator control plane.
Runtime GovernanceHow the layers combine into governed execution.
Capability ControlAuthority, scope and payload binding before mutation.
Memory RuntimePersistent state, documents, activation and ledger provenance.
Control PlaneSource-to-runtime deployment evidence for operators.