The Vault is a method and component atlas for heads of engineering, so that a team reusing a mechanism inherits its assumptions and turns each open one into a test.
Retain the question, relevant prior work and explicit negative search results.
Proposed reuse and intended environment.
Retain the question, relevant prior work and explicit negative search results.
Claim and intended environment.
References, counterexamples and failed searches.
Negative searches and counterexamples remain part of the research record.
Discover typed candidates while distinguishing capability from working method.
Source-connected component/method candidates.
Discover typed candidates while distinguishing capability from working method.
Mechanism identity, ports and contracts.
Workflow identity, evidence and lineage.
A capability entry and a working method are different kinds of evidence.
Grade the specific claim and test whether the proposed verification can fail.
Specific claim, artifacts and existing evidence.
Actual harness/canary or reproduction result.
Actual result, including failure/refutation.
Grade the specific claim and test whether the proposed verification can fail.
Assertion/artifact/function/reproduction/replication remain distinct.
Refutations remain useful retained records.
A proposed verification must be able to expose a failure.
Compare typed interfaces, QoS and environmental assumptions.
Producer guarantees and consumer assumptions.
Evidence grade and refutations, not automatic compatibility.
Explicit age/absence behavior and remaining environment obligation.
Compare typed interfaces, QoS and environmental assumptions.
Type, cadence, absence and ordering.
Undischarged assumptions remain attached to the assembly.
Type compatibility alone does not discharge timing, ordering or environment assumptions.
Test the gap in the intended setting and retain the actual result for reuse.
A concrete gap to test in the target.
Independent behavior under the intended delayed/absent-input case.
Test the gap in the intended setting and retain the actual result for reuse.
Delayed/absent inputs and intended conditions.
Actual outcome and identified downstream use where available.
A target-setting evaluation is evidence for that setting; it is not general proof.
Proposed reuse and intended environment.
Retain the question, relevant prior work and explicit negative search results.
Claim and intended environment.
References, counterexamples and failed searches.
Negative searches and counterexamples remain part of the research record.
Source-connected component/method candidates.
Discover typed candidates while distinguishing capability from working method.
Mechanism identity, ports and contracts.
Workflow identity, evidence and lineage.
A capability entry and a working method are different kinds of evidence.
Specific claim, artifacts and existing evidence.
Actual harness/canary or reproduction result.
Actual result, including failure/refutation.
Grade the specific claim and test whether the proposed verification can fail.
Assertion/artifact/function/reproduction/replication remain distinct.
Refutations remain useful retained records.
A proposed verification must be able to expose a failure.
Producer guarantees and consumer assumptions.
Evidence grade and refutations, not automatic compatibility.
Explicit age/absence behavior and remaining environment obligation.
Compare typed interfaces, QoS and environmental assumptions.
Type, cadence, absence and ordering.
Undischarged assumptions remain attached to the assembly.
Type compatibility alone does not discharge timing, ordering or environment assumptions.
A concrete gap to test in the target.
Independent behavior under the intended delayed/absent-input case.
Test the gap in the intended setting and retain the actual result for reuse.
Delayed/absent inputs and intended conditions.
Actual outcome and identified downstream use where available.
A target-setting evaluation is evidence for that setting; it is not general proof.
An illustrative process for investigating claims, comparing contracts and retaining unresolved obligations.
Additional mechanisms are described in the technical reference.
Research traces lead to typed components and working methods. Evidence and falsifiers inform composition, while unmet assumptions remain obligations for a target experiment.
Connect a question to scientific references, prior work and explicit search results.
Keep evidence grades, counterexamples and negative controls with the mechanism.
Compare interfaces, timing and environmental assumptions before combining methods and components. Carry unresolved obligations into the target experiment with their evidence.
Build on more than a promising idea.
Discuss a research questionA team wants to combine a temporal memory component with a workflow. Matching function signatures is only the beginning.
The Vault connects components, methods, contracts, evidence and lineage. A component describes a mechanism. A method describes how work is performed. Both need enough context for another team to decide whether reuse is justified.
Negative findings belong beside successful candidates. A failed experiment can save another team from accepting an assumption that did not survive testing.
Typed ports describe interface compatibility; assume/guarantee contracts describe the environment that the component needs.
Check what a port accepts and produces, including cadence, absence and ordering where relevant.
A composition preserves obligations its parts have not discharged. Connecting two APIs cannot erase those requirements.
An unresolved timing or delivery assumption becomes a specific experiment against the intended environment.
The head of engineering decides whether to reuse; open assumptions become tests first. Illustrative.
What the research says
Research on judgment and on logging points the same way: a written rule and a small proof outperform memory and impression. The Vault gives each reusable mechanism its assumptions and test results, so a head of engineering checks them before a promising demo becomes a dependency.
Illustrative situations, connected to the mechanisms that make them possible.
R&D and software teams
A new problem may overlap earlier engineering in another project.
Research organizations
A plausible idea may reproduce known prior art or fail under a simple counterexample.
Institutions
A useful engineering result should survive its original author and project.
A catalog entry becomes more useful when another system can reproduce its effect and adopt it under stated conditions.
Recurring mechanisms across independently developed systems can suggest candidates for reuse. Their novelty, assumption independence and downstream value remain questions to examine.
Research, an accepted component and a patent have different evidential and legal meanings. Public examples use cleared material, and adoption is described only where an actual downstream use can be identified.
Documents support it, but its organizing units are mechanisms, methods, contracts and evidence. The goal is to make engineering knowledge usable in another system.
A technical question, source-backed alternatives, a falsifiable experiment, a reusable artifact with its contract, and an adoption decision grounded in the result.
The technical choices that give The Vault its particular behavior.
The Vault organizes reusable engineering as components, methods, contracts and evidence. Composition carries unresolved assumptions into the assembled system, where a test can determine whether reuse is justified.
Inspect the interface. Check what a port accepts and produces, including cadence, absence and ordering where relevant.
Carry the assumption. A composition preserves obligations its parts have not discharged. Connecting two APIs cannot erase those requirements.
Turn the gap into a test. An unresolved timing or delivery assumption becomes a specific experiment against the intended environment.
An illustrative engineering investigation into whether two components can be composed.
Follow the storyWhich component would your team reuse if its assumptions came with it?
Discuss a research question