Return to the current task after checking the rules
Separate the Truth of public claims from task state and readback evidence, so proposals and demos are never presented as formal completion.
EVIDENCE / LOCALIZED DECISION BRIEF
Truth describes the validity of a public claim. Record and Receipt states describe one task version. They must never stand in for each other.
REFERENCE_ARCHITECTURE · REFERENCE_SUPPORT

The reference architecture binds decision sources, human approval, governed action and formal-state readback to the same task version. Truth can advance only after the Evidence gate passes.
The proposal retains its SourceRef, scope and task version.
Named approval neither crosses versions nor expands scope by default.
A system response records action state; it does not prove completion.
Independent verification reads formal state and binds an Evidence Owner.
REFERENCE ARCHITECTURE · SYNTHETIC ILLUSTRATION · NO PRODUCTION CONNECTION, CUSTOMER DEPLOYMENT OR IMPACT CLAIM

Action, receipt, validation, lineage and evidence package remain on one auditable trace.
SYNTHETIC PRODUCT UI · REFERENCE ARCHITECTURE · NO CUSTOMER DATA · NO PRODUCTION CONNECTIONPAGE ROUTE / evidence
Separate the Truth of public claims from task state and readback evidence, so proposals and demos are never presented as formal completion.
Separate the Truth of public claims from task state and readback evidence, so proposals and demos are never presented as formal completion.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Source-traceable reference
Compare the same operating fields before choosing a direction.
Confirm the owner, authority, human gate, and readback rule.
Define a baseline, target, owner, and observation window before claiming impact.