Implemented and observed in the stated scope
IMPLEMENTED_AND_OBSERVED
A specified behavior or state was observed in the recorded environment and window. This is not universal coverage or a fresh live-state claim.
Public scope and technical limits
A precise claim.
A visible boundary.
Public material explains architecture, authority and specific engineering results. Each result is bounded by its source, population and observation window.
Public scope
Architecture, authority and technical evidence.
Public material covers system architecture, authority boundaries and scoped technical evidence. Returns, balances and proprietary strategy parameters remain private.
Read the principles →Dated evidence boundary
Local behavior, installed identity and operating effect are separate.
The archived local repair records did not establish installed consumer revisions, natural completion or durable rollback with fresh output. The 1 October 2026 inspection did not establish the unified research-to-authority-to-execution evidence path across every engine. Those findings are historical observations; this publication does not substitute them for a new runtime census.
Internal review and public checksums do not constitute external attestation. Archived operating observations retain their original coverage and are not refreshed by a later test result.
Read the fixed historical records →How to interpret status
Not observed ≠ not implemented.
A verification limitation qualifies a particular claim. It is not automatically a verdict that the underlying function does not exist. Source presence alone also does not prove a reachable or verified execution path.
Implementation present; runtime effect not verified
IMPLEMENTED_NOT_RUNTIME_VERIFIED
Source, an installed-source inspection or a local candidate exists. The relevant natural consumer behavior or current operating effect has not been established.
Partial implementation or integration
PARTIALLY_IMPLEMENTED
Named paths exist, while another named part is incomplete, sealed or not connected. Read the exact gap rather than treating the whole system as absent.
Design only for this claim
DESIGN_ONLY
An intended responsibility or interface is described, without an implementation bound to this particular claim.
Unknown in the examined scope
UNKNOWN
The necessary source, observation or consumer identity was not available or not read. Unknown is neither permission nor evidence that a function is missing.
Not observed is not not implemented
Implementation existence, path reachability, a dated observation and verified operating effect are separate questions. Evidence that was not read cannot establish absence.
Not implemented
This requires evidence about a named searched code or execution scope. An unread artifact, a missing runtime observation or a design limitation alone is insufficient.
Observed in a limited scope
Keep the specific behavior, environment, original time and measured population. A refused attempt is a narrower observation than testing all accepted and refused cases.
Verified for a specific execution path
The actual consuming path, applicable inputs and accepted/refused or defective/corrected cases must be bound to the tested source and population.
Not universally established
Evidence for one path can coexist with missing coverage across other engines or markets. It does not erase the path that was actually examined.
Technical acceptance
Evidence that can support a stronger system claim.
Execution identity
Identify the installed revision and the component that actually consumes it. Bind a natural-run receipt to that revision and state its coverage.
Boundary enforcement
Exercise the real permission-consuming path with both allowed and refused inputs. A declared policy or a health summary alone does not establish enforcement.
Recovery behavior
Observe the affected component after recovery, including fresh domain output. Process presence and a successful restart command are separate observations.
Reproduction and review
Keep the input, source revision, test population and original failure. Distinguish an internal review from an independently runnable public reproduction.
These conditions are evidence requirements, not claims that they have already been met. Published local repairs retain their own adoption and reproduction limits.