Clear claims. Negative results included.
North Star’s public technical story should stay stronger than its marketing story: say exactly what was demonstrated, preserve constraints and negative results, and separate implemented behavior from research direction.
Implemented / evidenced
Witness and replay surfaces, semantic coordinate queries, dual-state review artifacts, Memory Diff, ANLS packets and deterministic storage benchmarking exist in the validated source lineage reviewed for this site.
Perception-first operating environment
The architecture points toward a system where observed state and accountable interpretation precede command authority. This phrase is a product/design framing, not an already-completed general-purpose OS claim.
Production readiness
No claim here implies autonomous truth, hidden self-improvement, customer-data readiness, live-provider authority, release authority or a completed production operating system.
Useful boundaries for technical readers.
These distinctions make the architecture easier to evaluate and keep the project from disappearing behind its own vocabulary.
It is memory, semantic state, replay and governance infrastructure around models.
Witnessed evidence and explanation receipts can still be incomplete or wrong.
Retrieval is only one surface; authority, contradiction, state differentiation, replay and governed promotion are first-class concerns.
ANLS targets semantic structure and auditability; mature byte compression remains better at raw byte reduction in the tested fixture.
Dual-state mechanics explicitly preserve unresolved disagreement.
Feedback and candidate state may inform preview behavior but do not silently mutate canonical memory.