FAQ and glossary
Resolve common questions and align the language used across guides, incidents, Community Source, and publications.
Frequently asked questions
Does OGO run commands?
The guide can reference and explain approved commands. Execution remains external and human-authorized. The record distinguishes reference, execution, captured result, and controlled change.
Is AI required?
No. The deterministic simulator and approved guide path work without AI. Optional AI output does not become proof unless an operator verifies and commits supporting evidence.
Is the hosted product free?
Yes. The public hosted Studio remains free to explore without creating an account.
Does hosted access include the complete source?
No. Complete current source, local deployment, private repository membership, full guide-library access, and contribution access use the verified OGO Community Source workflow.
Is OGO Community Source open source?
No. It is a verified private-source collaboration and adoption program. OGO Private Open Development, or OGO POD, describes collaborative development with complete source limited to approved recipients.
What happens to copies previously distributed under MIT?
They retain the rights already granted for those copies. A private repository or later agreement does not retroactively erase an earlier MIT grant.
Does submitting the application grant access?
No. Verification, the correct executed terms, manual approval, GitHub identity confirmation, and a recorded least-privilege invitation are required.
Is a fault boundary the same as root cause?
No. A boundary is the smallest supported area where the evidence places the problem. Root cause may require additional engineering, reproduction, or vendor analysis.
Why keep PDF and DOCX files?
They provide fixed offline editions for workshops, review, records, and users who cannot access the hosted site. The hosted documentation remains the current searchable source.
Glossary
Community Source: Verified private-source access to the complete current OGO application under executed terms. OGO POD: OGO Private Open Development; collaborative development with complete source limited to approved recipients. Verified access: The application, review, agreement, approval, and least-privilege invitation process. Evidence gate: A question whose supported answer changes the route. Committed evidence: An observation the operator has accepted into the incident path. Candidate boundary: A technical or ownership area still supported by current evidence. Owner route: The person or team responsible for the next evidence, decision, action, or validation. Safety gate: Conditions that must be satisfied before a controlled action. Exit proof: Measurable evidence that the original impact has recovered. Dossier: A stable decision-ready incident and escalation record. Healthy peer: A comparable unaffected path, asset, site, service, or workload used to narrow differences.