Work and evidence
The state of the work matters.
Deployed, demonstrated, and planned are not synonyms. This page explains how ExistX distinguishes those states and what a public work record contains.
Status definitions
Five evidence states
The state tells you what has actually happened: operational use, a bounded demonstration, active development, planned work, or a conceptual model.
- Deployed
- In use within a named operational boundary, with an approval basis stated to the extent releasable.
- Demonstrated
- Shown to work in a named test, laboratory, or representative environment — with its limitations stated.
- In Active Development
- Currently being engineered toward a defined demonstration or delivery milestone.
- Planned
- Committed future work with a defined scope, shown only when strategically useful and clearly labeled.
- Conceptual
- A taxonomy label or design concept. Not evidence that the capability currently exists.
The record model
What every published record states
A useful record makes the result traceable to its owner, environment, boundary, and limitations.
- What was done and the claim the record supports
- Attribution: corporate, team or key personnel, partner, or research provider
- Date and environment, named to the extent releasable
- System boundary and method
- Result, bounded to what was actually shown
- Limitations and residual uncertainty
Attribution
Whose work a record describes
Experience and results keep their attribution.
Corporate
Work performed by ExistX as an organization.
Team and key personnel
Experience individuals bring from prior roles, identified as team or key-personnel experience.
Partner
Work performed with or by a partner, with the partner’s role identified.
Galois research
Research assets from the Galois-to-ExistX pipeline retain Galois attribution. Galois provides research; ExistX operationalizes.
Published records
Public work collections
Only released records appear in the public collections.
Related
From evidence back to the engineering
Next step
Discuss the evidence you need
If your evaluation depends on a specific property, environment, interface, or assurance artifact, bring that requirement to the technical discussion.
Do not include classified, controlled, proprietary, export-controlled, or customer-sensitive information in any message sent through this site.