Check a precise historical claim.
A patent record or public profile provides an independent reference. The record supports the claim within its scope; a family recollection remains a separate first-person account.
EVIDENCE / PROVENANCE
Follow the claim.
Inspect its support.
A source tells you where a statement came from. Its scope tells you what you can reasonably conclude. Use the source inspector to check both while staying with the page.
READING THE EVIDENCE
Different sources answer different questions.
Understand the experience behind the work.
The farm and early-computing stories are my recollections. A public record may support a related detail without independently verifying every remembered event.
Read the systems-lineage story ↗Inspect the mechanism and its limits.
A working example, architecture model, or test can demonstrate a defined behavior. Its accompanying scope identifies whether it is executable, scripted, synthetic, or part of private research.
Inspect Axiom’s public examples ↗Separate current work from the next question.
A research direction or application draft describes work in progress. Read its stated status alongside the available artifact before treating an intended capability as implemented.
Read the invention-development status ↗USING THE SOURCE INSPECTOR
Keep the claim and its context together.
Open a source control to see the source type, the limited claim it supports, its verification status, and an original reference when available. Close the panel to return to the page.
Provenance preserves origin. It helps you assess a claim; it does not make every stored assertion correct.
Compare three examples.
A public patent, a professional profile connected to a personal story, and an authored architecture model offer different kinds of support.
FROM SOURCE TO NEXT STEP
Ask what the evidence establishes.
The Navigator demonstration uses synthetic records to make workflow status and ownership inspectable. That supports an operational question—who needs to act—without establishing whether a security control is effective.
Follow a total into the synthetic records ↗When support is incomplete.
Keep the unknown visible. Find the missing observation, check the requirement, or ask for a walkthrough of the relevant implementation before accepting a broader conclusion.
Explore how Control Intent frames that question ↗AXIOM / IMPLEMENTATION AND EVIDENCE
Completed work.
Clear sources for each claim.
I completed Axiom's move from the earlier Bedrock/Titan embedding connection to local Arctic embeddings and a fresh Claude instance. I tested retained memory, retrieval and weighted context in the replacement setup and resumed useful prior context.
This is my firsthand implementation and testing account. Private migration test artifacts are not published on this site.
An earlier September 18, 2026 archive documents migration design and bounded tests. Review independently recomputed 31,286 eligible source identities and 37,835 expected chunks from its corrected manifest. Those figures describe the historical migration scope rather than a retrieval-quality score.
The public context resolver executes defined rules; the model-swap illustration is scripted. Neither substitutes for the private completed tests or promises identical answers across models.
Read the completed migration account