The Questions Before the Answers: A Charter for the Work That Follows
Frames the inquiry: before a system can answer “trusted,” it must ask what kind of claim is being made, what supports it, and what consequence follows.
Published research
Read in numerical order for the full progression, or enter through the failure mode you are trying to reason about: identity, proof, evidence, authority, memory, recovery, uncertainty, or time.
CoreBond.io provides direct access to the research PDFs. DOI links below remain the archival publication records.
The charter for the inquiry and the questions that shape the series.
Frames the inquiry: before a system can answer “trusted,” it must ask what kind of claim is being made, what supports it, and what consequence follows.
Governance, device identity, credential lifecycle, authentication, and time-dependent decisions.
Separates the presence of an audit record from the stronger claim that a governed actor, authorized action, or trustworthy decision has been established.
Questions systems that let a device self-assert identity, and pushes identity toward externally governed assignment, proof, and verification.
Examines the operational cost of credentials across issuance, storage, rotation, revocation, replacement, recovery, and retirement.
Distinguishes a credential from proof, a proof from an authentication result, and a result from an enduring authorization.
Looks at Zero Trust decisions as time-bound outcomes that depend on fresh inputs, available dependencies, and responsible failure behavior.
Behavioral evidence and the boundary between what is observed and what may responsibly be concluded.
Treats observed behavior as evidence that may inform identity-related decisions without collapsing behavior into identity itself.
Draws a hard line between what evidence shows, what it merely suggests, and what a decision-maker is allowed to conclude from it.
Where authority applies, where it stops, and why conclusions cannot borrow authority they were never given.
Shows why a valid decision in one scope cannot be carried into another scope as if its authority automatically came with it.
The role of retained state, controlled recovery, and incomplete knowledge in later decisions.
Explains why retained state can help a system remember prior context but cannot by itself authorize a new consequence.
Treats recovery as a bounded trust decision: what may be restored, under whose authority, from which evidence, and with what remaining risk.
Makes uncertainty explicit so trust decisions can account for incomplete, stale, conflicting, or unavailable evidence.
Extending trust analysis across time instead of treating one decision as permanent.
Extends the series into ongoing evaluation, where trust must be maintained, revised, or withdrawn as conditions change.