ODA

Policy

How Oda is governed

Written rules the system actually follows. Mapped to NIST AI RMF and ISO/IEC 42001 language — not a certification claim.

Operating policy

GPU tenancy. The RTX 5080 belongs to the main model alone. The Intel Arc B580 runs the desktop, other apps, and on-demand vision. The memory service runs on CPU. Photo and writing jobs are scheduled apart so they never compete for a card.

Public demo isolation. The members chat has no tools, no memory, every approval set to deny, a two-turn cap, and private network addresses blocked. It cannot read or write private memory.

Scheduled work runs; exceptions wait for a human. The daily paper publishes on schedule only after it clears every gate. Recovery runs, republishing, and corrections stop and wait for a human decision.

Secrets out of model context. Credentials live in locked files that scripts read at run time. They never go into prompts, agent charters, or the public demo.

Local-first data boundary. Inference and long-term memory run on hardware I own. Cloud assistants are separate tools and do not hold the house memory.

Content gates. Editorial gates reject bad drafts, and the paper rewrites instead of quitting. Fake or tiny lead images fail loud. A quote gate, added after we caught fabricated quotes in our own output, now strips any quote without a named speaker and a fetched source.

Framework mapping

Controls on this page are mapped to NIST AI RMF 1.0 functions (Govern, Map, Measure, Manage) and ISO/IEC 42001:2023 areas (clauses 4–10 and Annex A objectives such as policies, resources, lifecycle, data, and use). This site does not claim certification, audit completion, or EU AI Act conformity assessment.

ControlNIST AI RMFISO/IEC 42001 (mapped)
GPU tenancy and job schedulingGovern, Map, ManageCl. 6 Planning, Cl. 8 Operation; A.4 Resources
Public demo isolationGovern, Map, ManageCl. 8 Operation; A.6 Life cycle, A.9 Use, A.10 Third parties
Human decision on exceptionsGovern, ManageCl. 5 Leadership, Cl. 8 Operation; A.9 Use
Secrets out of model contextGovern, Map, ManageCl. 7 Support; A.2 Policies, A.7 Data
Local-first data boundaryMap, ManageCl. 4 Context; A.4 Resources, A.7 Data
Content gates, including the quote gateMeasure, ManageCl. 8, Cl. 9 Evaluation, Cl. 10 Improvement; A.5 Impact, A.6 Life cycle
Interrupt alerts and recovery playbooksMeasure, ManageCl. 9, Cl. 10; A.6 Life cycle
Blameless postmortemsGovern, ManageCl. 10 Improvement; A.5, A.6
Update snapshots and patch restoreGovern, Measure, ManageCl. 8, Cl. 9; A.6 Life cycle
Written charters for each specialist agentGovern, MapA.2 Policies, A.3 Internal organization, A.9 Use
Red-team testing of the public demoMeasureCl. 9 Evaluation; A.5, A.6

Related

Incidents Red team Stack