Open Engineering Questions

This summary is currently under reconciliation. The workspace still contains unresolved drift between specification pages, engineering fact sheets, OpenAPI, and implementation code.

Status Under Review

Do not treat this page as evidence that the specifications are implementation-complete or enterprise-ready. A workspace audit on 2026-03-15 found material gaps between documented claims and the current codebase, including API scope, agent capabilities, auth behavior, and event pipeline guarantees.

---

Summary

Item	Status
Original docs backlog size	48 tracked engineering-gap items referenced in docs
Workspace reconciliation	In progress
IMPLEMENTATION_FACTS.md	Not yet a fully verified implementation source of truth
API_FACTS.md	Not yet a fully verified API source of truth
OpenAPI v1.0.0 claims	Require code-level reconciliation

---

Resolution Status

The original docs rollout marked the following sections as resolved, but that status is no longer considered authoritative until the reconciliation work is complete:

• System Overview — status under review
• Device Agent — status under review
• Detection Engine — status under review
• Context Risk Engine — status under review
• Policy Engine — status under review
• Event Pipeline — status under review
• API Contract — status under review
• Privacy Model — status under review
• Telemetry Schema — status under review
• Threat Intelligence — status under review
• Scope & Nicht-Ziele — status under review

Current Focus

The current engineering reconciliation is prioritizing:

• API surface and path/versioning drift
• authentication and tenant-isolation drift
• event, threat, alert, and device schema alignment
• agent capability claims vs. actual collector/runtime scope
• event-store, retention, and integrity guarantees

See the internal workspace audit and backlog for the current remediation order.

---

Enterprise-Ready Criteria

• Specification pages reconciled with current implementation
• Engineering fact sheets verified as current and canonical
• OpenAPI, API docs, and server routes are mutually consistent
• Critical doc/code drift findings resolved
• Security review completed with no P1 findings
• CI pipeline enforces contract consistency