Evidence Explorer
Open the claim.
Inspect what supports it.
Recorded results, architecture questions, and proposed comparisons—each with its source and scope.
Dated execution or test evidence.
Architecture, governance, role, or scope.
A comparison or integration to test.
Type identifies the source. State and ceiling identify what it supports. TESTED does not mean independently validated.
Evidence state unavailable — no claim promoted.
DVSdvs-two-host · v1TESTEDTwo connected computersDated in-house execution evidence.SUPPORTED WITH BOUNDS
- Claim
- Selected allowed and blocked actions behaved differently on a tested two-computer path.
- State
- SUPPORTED WITH BOUNDS
- Evidence
- A recorded June 6, 2026 test sent one allowed action to a receiving computer and its protected target. The blocked action appeared zero times at both. Both computers were controlled by the founder.
- Ceiling
- This is an in-house result on the tested path. It does not establish customer deployment, independent reproduction, whole-application coverage, or general production effectiveness.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Recorded in-house test · public source summary
Inspect public detail
Carried forward from the existing public Evidence page; original test date June 6, 2026. The private raw test artifacts are not published here.
View the versioned public records (JSON)DVSdvs-local · v1TESTEDLocal approval checksDated in-house execution evidence.SUPPORTED WITH BOUNDS
- Claim
- A focused local rerun recorded an allowed request reaching the tool and specified invalid requests producing no tool calls.
- State
- SUPPORTED WITH BOUNDS
- Evidence
- A May 30, 2026 rerun recorded 11 passing tests. The valid request reached the tool once. Changed approval records, missing approval, and reuse attempts produced zero calls to the tool on that tested path.
- Ceiling
- Eleven tests are a bounded local observation, not a universal success rate or proof against every route or failure mode.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Recorded in-house test · public source summary
Inspect public detail
Carried forward from the existing public Evidence page; original rerun date May 30, 2026. No new rerun is claimed by this page update.
View the versioned public records (JSON)DVSdvs-historical · v1DECLAREDSupporting historical reportSecondary test report; original record unavailable.NEEDS EVIDENCE
- Claim
- A supporting historical report describes one authorized send and six rejected hostile requests.
- State
- NEEDS EVIDENCE
- Evidence
- A later source-based report describes six HTTP 403 responses with the protected target unchanged during those attempts.
- Ceiling
- The standalone original closeout was not available in the reviewed material. This remains supporting historical reporting; the original result is not independently verified here.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Secondary historical report
Inspect public detail
Retained from the existing public Evidence page. Original closeout date and standalone artifact remain unavailable in this public record.
View the versioned public records (JSON)ORPHARDorphard-scope · v1DECLAREDTrajectory and recoveryArchitecture, role, scope, or source statement.OPEN QUESTION
- Claim
- Orphard frames trajectory and recovery as a control problem distinct from release authority.
- State
- OPEN QUESTION
- Evidence
- The public architecture defines checks on whether continuing work remains inside an evidenced operating envelope, with reconciliation or recovery when it diverges.
- Ceiling
- Architecture and design scope only. Comparative recovery performance, customer deployment, and independent reproduction are not established by this record.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Public architecture specification
Inspect public detail
Public scope adopted September 12, 2026. The scripted model is not experimental outcome evidence.
View the versioned public records (JSON)PORTFOLIOCONTROLportfoliocontrol-scope · v1DECLAREDLive orchestration and controlArchitecture, role, scope, or source statement.SUPPORTED WITH BOUNDS
- Claim
- PortfolioControl is the live orchestration and control implementation for these control questions.
- State
- SUPPORTED WITH BOUNDS
- Evidence
- The published architecture assigns PortfolioControl the role of examining control behavior in continuing work and returning observed problems to research.
- Ceiling
- Supports the stated role, not measured control effectiveness. Private operating state and customer validation are not supplied by this record.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Public architecture and role declaration
Inspect public detail
Role declared September 12, 2026. This page contains no public-safe current telemetry feed.
View the versioned public records (JSON)CRIMSON DELTAresearch-scope · v1DECLAREDSeparately governed researchArchitecture, role, scope, or source statement.SUPPORTED WITH BOUNDS
- Claim
- Crimson Delta connects research questions while programs remain separately governed.
- State
- SUPPORTED WITH BOUNDS
- Evidence
- The public research structure separates program claims and treats constellation links as methodological or problem relationships.
- Ceiling
- An organizational and methodological statement, not scientific validation or authority transfer between programs.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Public research-governance statement
Inspect public detail
Public scope adopted September 12, 2026. Open R&D does not imply an open-source license for every component.
View the versioned public records (JSON)DVS + ORPHARDjoint-delta · v1PROPOSEDA bounded joint comparisonComparison or integration not yet established.OPEN QUESTION
- Claim
- A bounded joint integration can test whether these controls add value over the strongest competent baseline.
- State
- OPEN QUESTION
- Evidence
- The proposed method compares one workflow against existing controls, measures both useful effects and costs, and preserves negative or inconclusive results.
- Ceiling
- A proposed comparison, not a completed partner result or demonstrated demand. No incremental operational benefit is claimed before measurement.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Proposed comparative method
Inspect public detail
Public method defined September 12, 2026. No partner outcome is attached to this record.
View the versioned public records (JSON)DVS + ORPHARDenterprise-continuity · v1PROPOSEDThe enterprise continuity contractComparison or integration not yet established.OPEN QUESTION
- Claim
- Consequential Action Continuity is the proposed contract connecting delegation, state seen, proposal, release, and observed effect.
- State
- OPEN QUESTION
- Evidence
- The proposed enterprise architecture separates a generalized control-plane core, a Latchboard-derived operator interface, DVS release authority, Orphard supervision, and execution through existing enterprise systems.
- Ceiling
- A synthesis and differentiation hypothesis. A complete enterprise implementation, connector coverage, comparative advantage, purchase demand, and end-to-end effectiveness are not established by this architecture.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Proposed enterprise architecture
Inspect public detail
Founder-directed synthesis supplied September 12, 2026. Component descriptions do not transfer validation to the combined system.
View the versioned public records (JSON)LATCHBOARDlatchboard-scope · v1DECLAREDThe operator interaction modelArchitecture, role, scope, or source statement.SUPPORTED WITH BOUNDS
- Claim
- Latchboard supplies a reference interaction model for bounded human/agent work.
- State
- SUPPORTED WITH BOUNDS
- Evidence
- The existing public demonstration describes AI-proposed task edits, review, stale proposals, ended delegation, and repeated review attempts. The enterprise direction carries those interaction principles into a separate operator console.
- Ceiling
- The reference workflow does not establish enterprise security, external-action control, or a validated generalized backend. Its proposed console role is distinct from the control-plane core.
- Updated
- · UNKNOWN · dated snapshot
- Source class
- Public demonstration description and proposed interface role
Inspect public detail
Existing public Latchboard description retained; enterprise role added September 12, 2026. No new empirical test is claimed.
View the versioned public records (JSON)No public record matches this selection. Absence of a result is not a positive result.
Current scope and what is not yet established
A working private DVS implementation exists. Initial in-house tests are complete; broader testing is underway. No customer pilot or revenue is established in the reviewed evidence.
- Customer validation. No customer deployment or payment is claimed.
- Another party’s production use. DVS has not been established in another party’s production environment.
- Independent reproduction. No independent external reproduction is claimed.
- Certification. No security, compliance, regulatory or government certification is claimed.
- Production identity and record storage. Managed identity and key services, organization-controlled decision records, and shared tracking of reused approvals remain integration work.
- Coverage across an application. A deployment must find other routes to the same action, remove or control them separately, or explicitly exclude them before claiming coverage of the whole system.
- Completion and observed results. A DVS decision to allow an action does not prove that the receiving system completed it or produced the intended effect. Strong guarantees when records can change require checks at the receiving system and separate confirmation of the result.
How dates and freshness work
UPDATED is the public record’s review date. Historical test dates are named separately; republishing a result does not mean it was rerun.
CURRENT means this public snapshot is no more than 30 days old. After 30 days it displays STALE. An unavailable or invalid date, an unavailable record, or a disabled date check displays UNKNOWN. Freshness is editorial, not a claim that the system was retested.
The embedded records remain readable without JavaScript. If the public evidence file fails validation, the interface shows: Evidence state unavailable — no claim promoted.
Build with unFragged
Bring one workflow. Build the evidence together.
Establish the strongest competent baseline. Integrate where a residual control gap remains. Measure the delta. Keep a clean negative result if the existing stack already solves it.
Partner with unFragged