EVULGARE

Institutional evidence record

EVI-INST-0007

Contact submissions are distinct from passive browsing

The repository stores information a visitor voluntarily submits through the contact form; this is a different processing event from ordinary public-page browsing.

Source and verification

Full bounded record

Return to the ledger
Claim ID
EVI-INST-0007
Claim class
REPOSITORY VERIFIABLE
Status
SUPPORTED WITHIN SCOPE
Institutional page
Privacy
Source type
REPOSITORY SOURCE
Source release
2.0.0-rc.57-WIP
Source path or public URL
app/models.py
Source digest
5ef02293bd2c414b8cb64b7bfcc214b4a446118324b942ced2d030cdfccb735a
Observation environment
RC57 source tree
Observation time
2026-08-13T00:47:38Z
Verification method
Contact model and route inspection
Verification result
ContactSubmission fields and write path present
Scope
Packaged data model and route behavior
Change event
EV-CHG-0056-005
Public record URL
https://evulgare.com/institutional/evidence/EVI-INST-0007/

Scope control

Limitations

  • Actual production database contents, access, backup, deletion, and infrastructure logs were not observed.

Review triggers

Known defeaters

  • Production configuration or a different deployed version can change storage behavior.

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-0056-005

    Visitor-supplied contact data is treated as a separate processing event.

    Reason
    Separate voluntary contact submissions from passive browsing.
    Previous state
    Collection behavior not fully explained
    New state
    Submission and passive-browsing states described separately
    Review boundary
    Production database and logs not observed
    Source record
    app/models.py

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.