Route 168 of 176
Codex Lifecycle State
QRCompliance.us · Validation Layer · Source of truth: QRCodex.us
Summary
A registered identity's compliance condition — valid, non-compliant, revoked — is not the same thing as where its record sits in the operational lifecycle of QRCodex.us. A record can be newly created, actively scanned, dormant, superseded, or archived, independent of whatever its current compliance condition happens to be. Codex Lifecycle State is the tracking of that record-level stage, and it exists as a distinct concept precisely because collapsing it into compliance state would blur two questions that need separate answers.
QRCompliance.us determines whether a condition is currently satisfied. QRCodex.us separately tracks where a record sits in its own operational lifecycle. A record can be Active while its compliance condition is Non-Compliant, and Archived while its last known compliance condition remains Compliant — the two states move independently.
It is easy to assume that a registered identity's record has essentially one axis of change: compliant or not, valid or revoked. In practice, the record itself moves through a lifecycle that has nothing directly to do with that axis. A record is created, it becomes active as scans and transactions reference it, it may go dormant if the identity stops being used, it may be superseded by a successor record, and eventually it may be archived. Each of those stages is a fact about the record's operational status inside QRCodex.us, not a fact about whether the identity currently satisfies compliance requirements.
Keeping these two tracks separate matters because they answer different practical questions. Compliance state answers 'is this identity currently allowed to proceed.' Lifecycle state answers 'where does this record sit in its operational life, and what kind of interaction with it makes sense right now.' An archived record's compliance condition at the moment of archival remains part of the historical record, but nobody should expect an archived record to be actively re-evaluated the way an active one is.
This route defines the lifecycle states QRCodex.us tracks, how a record moves between them, and how lifecycle state stays cleanly independent of the compliance determinations made by QRCompliance.us. Confusing the two would either strip meaning from an inactive record's last known compliance condition, or force ongoing re-evaluation of records that no longer need it.
01Plain-English Definition
Codex Lifecycle State is the operational stage a registered identity's record occupies within QRCodex.us — created, active, dormant, superseded or archived — tracked independently of the compliance condition QRCompliance.us determines for that identity at any given time.
Lifecycle state is a property of the record as an operational object. Compliance state is a property of the identity as a subject of validation. The two are stored, tracked and updated through entirely separate logic, even though both are visible together whenever a record is consulted.
This distinction is not a technicality. It is what allows a dormant record's historical compliance condition to remain meaningful without implying the identity is still being actively checked, and it is what allows an actively used identity's compliance condition to change repeatedly without ever touching the fact that its record remains in an Active lifecycle stage throughout.
02The Lifecycle Stages
QRCodex.us recognizes a defined set of lifecycle stages that a record can occupy, each with its own entry conditions and its own implications for how the record is treated operationally.
| Lifecycle Stage | What It Means |
|---|---|
| Created | A record exists in Codex following registration but has not yet been referenced by a live scan, access check or transaction. |
| Active | The record is being referenced by ongoing scan, access or transaction activity within the defined activity window. |
| Dormant | No activity has referenced the record within the defined window, but it has not been formally superseded or archived. |
| Superseded | A successor record has replaced this one — for example following a renewal or a re-registration — and this record now points to the successor. |
| Archived | The record is retained for historical and audit purposes only and is no longer expected to receive live activity. |
None of these stages describes whether the underlying identity is currently compliant. A record can enter Dormant while its last determined compliance condition was fully satisfied, and a record can remain Active for years while its compliance condition changes many times across that span.
03Practical Value
Separating lifecycle state from compliance state produces practical benefits for how the system allocates its attention and interprets its own history.
Correct allocation of re-evaluation effort
Active records are the ones where real-time compliance changes matter most operationally; dormant and archived records do not need the same ongoing attention, and lifecycle state is what signals that difference.
Historically meaningful archives
An archived record retains its last known compliance condition as a fact of record, without implying that condition is still being asserted as current.
Clean handling of succession
When a record is superseded, lifecycle state carries the operational continuity forward to the successor record without needing to reinterpret or restate the prior compliance history.
04Operational Flow
A record's lifecycle state changes according to its own operational triggers, running alongside — but never merged with — whatever compliance determinations occur during the same period.
- 1Record createdRegistration produces a record in QRCodex.us, entering the Created stage before any live activity references it.
- 2First activity moves it to ActiveThe first scan, access check or transaction referencing the identity moves the record into the Active stage.
- 3Activity window monitoredOngoing activity is tracked against a defined window; the record remains Active as long as that window keeps being refreshed by new activity.
- 4Inactivity or succession detectedIf the activity window lapses, the record moves to Dormant; if a successor record is created, this record moves to Superseded.
- 5Archival applied when appropriateA Dormant or Superseded record that meets defined retention conditions moves to Archived, retained for audit without further active tracking.
Lifecycle state tracks the record's operational life. It never tracks, and is never used as a substitute for, the compliance condition of the identity that record represents.
05Lifecycle State Versus Compliance State
Because both states are visible whenever a record is consulted, it is important to be precise about which question each one answers.
| Aspect | Lifecycle State (Codex Operations) | Compliance State (Validation) |
|---|---|---|
| Answers | Where does this record sit in its operational life | Is this identity's condition currently satisfied |
| Determined by | Activity patterns, succession events and retention rules within QRCodex.us | Evaluation of evidence and requirements by QRCompliance.us |
| Changes when | Activity resumes or lapses, a successor record is created, or retention conditions are met | New evidence, a trigger event, or a scheduled review changes the underlying condition |
| Independent movement | Can be Active while compliance condition is Non-Compliant, or Archived while last condition was Compliant | Can change repeatedly while lifecycle state remains unchanged at Active throughout |
| If they appear to conflict | There is no real conflict — they are answers to different questions and are not compared against one another | Compliance determinations are never reinterpreted based on lifecycle stage |
A record's lifecycle stage never overrides, implies, or substitutes for its compliance condition, and the reverse is equally true.
06Archival and the Historical Record
Archival is the lifecycle stage most likely to be misunderstood, because it can look like a judgment about the identity rather than a statement about the record's operational status.
- An archived record is not deleted; it is retained precisely so that its full history remains available for audit.
- Archival does not assert that the identity is no longer valid, revoked, or otherwise compliance-affected — it asserts only that the record is no longer subject to active operational tracking.
- The last compliance condition recorded before archival remains attached to the record as historical fact and is not altered by the archival event itself.
- A record can, in defined circumstances, move out of Archived and back into Active if a legitimate need to reference it operationally arises again.
- Archival timing is governed by retention rules set at the governance layer, not by any judgment QRCodex.us makes about the identity's compliance history.
This is why an auditor reviewing an archived record needs to read both fields independently: the lifecycle stage explaining why the record is no longer active, and the last compliance condition explaining what was true of the identity at the point activity stopped.
07System Relationship
System Chain — Six Locked Entities
- 1QuickResponseCode.usRoot / System EntryPublic entry point to the QR infrastructure.
- 2QRProtocol.usGovernance (Rules)Writes and governs the applicable rules.
- 3QRCompliance.usValidationValidates compliance readiness against applicable rules and conditions.
- 4QRCertified.usCertification AuthorityAuthorizes the QR for certification.
- 5QRRegistered.usRegistration ResultMandatorily registers the authorized QR.
- 6QRCodex.usOperations / RecordsRecords, operates, logs and preserves canonical operational truth.
No registration → no certified QR output.
Codex Lifecycle State is an operational concept native to QRCodex.us, but every layer above it interacts with it in a defined and limited way.
| Layer | Relationship To Codex Lifecycle State |
|---|---|
| ROOT — QuickResponseCode.us | Establishes the base identifier that persists across every lifecycle stage a record moves through, including archival. |
| GOVERNANCE — QRProtocol.us | Sets the retention rules and activity-window definitions that determine when a record moves between lifecycle stages. |
| VALIDATION — QRCompliance.us | Determines compliance conditions independently of lifecycle stage and does not adjust its evaluation based on a record's current lifecycle state. |
| AUTHORIZATION — QRCertified.us | May treat a Dormant or Archived record's certification as requiring renewal activity before further certified use, without that treatment implying anything about the historical compliance condition. |
| REGISTRATION — QRRegistered.us | Registration status persists independently of lifecycle stage; a dormant record's registration is not automatically withdrawn by dormancy alone. |
| OPERATIONS — QRCodex.us | Owns and tracks lifecycle state directly as part of the canonical operational record for every registered identity. |
Where any layer's treatment of a record appears to depend on lifecycle stage in a way that contradicts the recorded compliance history, Codex's record of both states governs the review.
What This Does — And Does Not — Do
Does
- ✓Track the operational lifecycle stage of a registered identity's record within QRCodex.us
- ✓Move a record between Created, Active, Dormant, Superseded and Archived stages according to defined triggers
- ✓Retain an archived record's last known compliance condition as part of its permanent history
- ✓Keep lifecycle state changes entirely independent of compliance determinations made by QRCompliance.us
- ✓Allow a record to move back out of Archived into Active when a legitimate operational need arises
- ✓Apply retention and activity-window rules set at the governance layer rather than ad hoc judgments
Does Not
- ✕Use lifecycle stage as a substitute for, or indicator of, current compliance condition
- ✕Alter a recorded compliance determination when a record's lifecycle stage changes
- ✕Delete an archived record's history rather than retaining it for audit
- ✕Allow QRCompliance.us to adjust its evaluation logic based on a record's lifecycle stage
- ✕Treat dormancy or archival as an automatic withdrawal of registration or certification status
- ✕Merge lifecycle state and compliance state into a single undifferentiated field
Related Routes
Common Questions
Does an Archived record mean the identity is no longer compliant?
No. Archival is a statement about the record's operational status, not about compliance. The last recorded compliance condition remains attached to the record as history, unaffected by archival.
Can a record be Active while its compliance condition is Non-Compliant?
Yes. Lifecycle state and compliance state move independently. An actively used identity can carry a Non-Compliant condition, and its record remains Active as long as it continues to be referenced by live activity.
What moves a record from Dormant back to Active?
A legitimate new scan, access check or transaction referencing the identity can move a Dormant, and in defined circumstances even an Archived, record back into Active.
Who decides the retention rules that trigger archival?
Retention and activity-window rules are set at the governance layer, QRProtocol.us, not decided ad hoc by QRCodex.us or QRCompliance.us on a case-by-case basis.
Does dormancy automatically withdraw registration or certification?
No. Dormancy is a lifecycle fact about the record. Registration and certification status persist according to their own rules and are not automatically withdrawn simply because a record has gone dormant.