The Evidence Standard Framework
Relevant source files
The following files were used as context for generating this wiki page:
The Evidence Standard Framework defines a taxonomy for labeling software claims, project statuses, and system capabilities based on verifiable backing. It establishes a project-wide commitment to distinguish between existing artifacts, active development, and future intent. The framework ensures all technical work remains inspectable and prevents the presentation of hypothetical features as completed products.
Sources: README.md:46-49, index.html:167-169, about.html:79-79
Core Taxonomy
The framework categorizes all claims into three distinct levels of verification. This classification applies to portfolio projects, Generative Engine outputs, and professional service deliverables.
Classification Levels
| Level | Definition | Backing Requirement |
|---|---|---|
| VERIFIED | The claim describes a completed and observable feature. | An artifact, test result, or direct observation. |
| STAGED | The claim describes a feature currently in development. | Active code commits or detailed technical documentation. |
| PLANNED | The claim describes a future goal or intended feature. | Stated intent or roadmap entry without active code. |
Sources: README.md:46-49, index.html:167-169, showcase/registry.json:4-10
Categorization Flow
The following diagram illustrates how the system classifies a technical claim based on available evidence.
Sources: README.md:46-49, about.html:79-79
Implementation in System Components
The framework integrates directly into project registries, work displays, and generative synthesis engines.
Showcase Registry Integration
The registry.json file uses the Evidence Standard to track the state of every artifact in the Dynamic Inner World Showcase. Each entry contains an evidence field that must match the framework taxonomy.
{
"added": "2026-09-28",
"description": "The full wiki exhibit of GestaltView v2...",
"evidence": "VERIFIED",
"file": "exhibit-wiki.html",
"id": "inner-world-exhibit",
"title": "Dynamic Inner World Exhibit"
}
Sources: showcase/registry.json:4-13
Work Evidence Lifecycle
In the work.html context, the framework supports a continuous loop of source preservation and relationship testing.
Sources: work.html:36-36
Generative Render Engine Provenance
The Generative Render Engine computes a "provenance envelope" for artifacts. This envelope includes a SHA-256 hash of the source material and labels the synthesis style, ensuring the rendered output remains evidence-based rather than hallucinatory.
Sources: showcase/render-engine.html:43-43, showcase/render-engine.html:162-171
Operational Commitments
The framework extends beyond software code to dictate how professional engagements and operations are conducted.
- Evidence before narrative: If receipts do not exist for a claim, the system labels it as interpretation or intent.
- Handoff, not dependency: Useful systems must leave the user more capable through documentation of known limitations and operating guidance.
- Correction as a feature: The user retains the power to correct, reject, or redirect the system. A system that cannot be corrected fails the evidence standard.
Sources: about.html:79-88, services.html:76-76
Engagement Workflow
- Discovery: Confirm constraints and available data.
- Fixed-Scope Proposal: Define deliverables and acceptance criteria.
- Milestone Build: Surface uncertainty early rather than burying it.
- Documentation Handoff: Provide operating guidance and known limitations.
Sources: services.html:76-76, services.html:168-175
Conclusion
The Evidence Standard Framework serves as the ethical and technical foundation for GestaltView and the associated portfolio. By mandating explicit labels for every technical claim, the framework ensures that software systems maintain accountability and that users can distinguish between proven capabilities and future development goals.