EVULGARE

Institutional evidence record

EVI-INST-0001

Canonical Institutional directory exists in the package

The packaged source defines a canonical /institutional/ route and repository-owned directory template.

Source and verification

Full bounded record

Return to the ledger
Claim ID
EVI-INST-0001
Claim class
REPOSITORY VERIFIABLE
Status
SUPPORTED WITHIN SCOPE
Institutional page
Institutional
Source type
REPOSITORY SOURCE
Source release
2.0.0-rc.57-WIP
Source path or public URL
app/blueprints/main/routes.py
Source digest
1cc285039e261460c4249372bf2f152416bbe4bf8c9a3995252db9543750bd0a
Observation environment
RC57 source tree
Observation time
2026-08-13T00:47:38Z
Verification method
Static route and template inspection
Verification result
Route declaration and template reference present
Scope
The identified source release only
Change event
EV-CHG-0057-001
Public record URL
https://evulgare.com/institutional/evidence/EVI-INST-0001/

Scope control

Limitations

  • Does not establish that the route is deployed or reachable on the current public host.

Review triggers

Known defeaters

  • Route removal, blueprint registration failure, mixed deployment, or stale host release.

Append-oriented lineage

Change history

Material claim changes are added as events. A correction, qualification, withdrawal, supersession, restoration, or stale marker should not silently erase the earlier state.

  1. CLARIFY

    EV-CHG-0057-001

    Visitors can now inspect support class, source, scope, limitations, and change history claim by claim.

    Reason
    Link the Institutional directory to a public evidence and change-history surface.
    Previous state
    Institutional directory without a claim-level public ledger
    New state
    Institutional directory plus stable claim records and change lineage
    Review boundary
    Repository package and separately identified actual-host observations
    Source record
    app/templates/institutional/evidence.html

Machine-readable record

Inspect the bounded JSON representation

The JSON endpoint contains the same public fields and change events. It does not add evidentiary weight or expand the record beyond this declared scope.

Open record JSON

MISSION-FIRST · EVIDENCE-LOCKED · MACHINE-SPEED

DETECT → VERIFY → DENY → CONTAIN → RECOVER → PROVE

Command integrity. Decision superiority. Compartment security. Attested reconstitution.