Engineering documentation lives in the docs/ tree of the data-laboratory repository. Developer-onboarding, runtime API references, and release manifests live on databhome.org/developer. This page is the entry point.

Architecture

• docs/PLATFORM_ARCHITECTURE.md — the four-layer model with per-layer code-path map.
• docs/PRODUCT_POSITIONING.md — what to say and what not to say about each product.

Agent design

• docs/ORULA_AGENT_V0.md — bounded intelligence agent endpoint table + behavior.
• docs/GU_AGENT_V0.md — bounded security agent endpoint table + behavior.
• docs/agents/BOUNDED_AGENT_DESIGN.md — the five enforcement layers, why reward is observational only in RC1.
• docs/agents/ORULA_REWARD_MODEL.md — field-by-field score schema.
• docs/agents/GU_REWARD_MODEL.md — same for Gu.
• docs/orula/ASSISTANT_WORKBOOK_KNOWLEDGE_MAP.md — how the NUT Ikorodu cooperative workbook becomes Orula's first knowledge source.

Marketplace + distribution

• docs/DATABHOME_PLATFORM.md — marketplace site spec.
• docs/DATABSYSTEMS_WEBSITE.md — this site's spec.

Security

• docs/security/ai-review-checklist.md — PR review gates.
• docs/security/ai-threat-model.md — eleven threats with mitigations.
• docs/security/ssh-hardening.md + deployment/security/ssh-hardening-baseline.sh — operator hardening.
• docs/security/remote-support-governance.md — Datab-staff access policy.
• Five incident runbooks under docs/security/runbooks/.

Release engineering

• docs/release/DATAB_NODE_RC1_RELEASE_NOTES.md — what's real, preview, planned.
• docs/release/RC1_OPERATOR_BOOT_GUIDE.md — twelve-step operator workflow.
• docs/release/RC1_KNOWN_ISSUES.md — honest catalog of known gaps.
• docs/release/RC1_VALIDATION_REPORT.md — refreshed per orchestrator run.
• docs/release/RC1_DEVELOPER_HANDOFF.md — phase plan for engineers picking up the work.