EVULGARE

IMPLEMENTATION RECORD · SYNTHETIC TECHNOLOGY DEMONSTRATION

Portable Acceptance Evidence Packets

Implementation record for deterministic, non-secret, non-persistent evidence packets that carry scoped host, device, XR, assistive-technology, security, performance, public-source, and independent-review results without automatically promoting a release.

Open the packet verifierOpen the packet schema APIResearch-to-software traceability →

Acceptance Evidence Packets — Evulgare 2.0.0-rc.9-WIP

Portable Acceptance Evidence Packets

The repository cannot reproduce every environment required for final acceptance. This subsystem carries bounded, non-secret evidence from actual hosts, representative browsers and devices, physical graphics/XR hardware, assistive technologies, security/privacy reviews, field performance measurements, and public-source reviews into a later repository review.

A valid packet proves schema and digest integrity only. It does not prove the stated test occurred, certify a real system, authorize operations, establish legal status, or promote a release.

Schema SHA-256: f55e3e1089bbed2565d3d3460ec4f2698a22712b7f93e541a598d6e93dbd1fc1
Contract proof SHA-256: 10445586c7aca3161d2a4f792bc4bcb4bfe90d37c9e0fc7e7cdf2a214df02320
Indexed reviewed packets: 0
Executed candidate packets awaiting review: 9
Evidence-ledger SHA-256: 87a4d46b5a12c98a37ba49cb16ea92430c0c5631078d44885764cd80fa136fe2

Independent evidence dimensions

Dimension Required checks Template
repository_build 5 docs/evidence/acceptance-packets/repository-build-template.json
production_host 10 docs/evidence/acceptance-packets/production-host-template.json
browser_device 6 docs/evidence/acceptance-packets/browser-device-template.json
physical_graphics_xr 7 docs/evidence/acceptance-packets/physical-graphics-xr-template.json
assistive_technology 7 docs/evidence/acceptance-packets/assistive-technology-template.json
security_privacy 9 docs/evidence/acceptance-packets/security-privacy-template.json
performance 10 docs/evidence/acceptance-packets/performance-template.json
public_source_review 7 docs/evidence/acceptance-packets/public-source-review-template.json
independent_claim_verification 7 docs/evidence/acceptance-packets/independent-claim-verification-template.json

Evidence boundaries

  • Executed checks must reference hash-addressed, bounded evidence artifacts.
  • Automated evidence may enter the candidate queue as EVIDENCE_READY_FOR_REVIEW; it is not reviewed acceptance.
  • PASS and PASS_WITH_QUALIFICATION require a recorded human review.
  • Secrets, credentials, cookies, raw external HTML, and unrestricted response bodies are prohibited.
  • Real coordinates, targets, weapon or payload commands, force authorization, terminal guidance, and vehicle-control fields are prohibited.
  • Public API verification is ephemeral and never writes a packet.
  • A packet always has promotion_effect: NONE; a later reviewed source release must make any release decision separately.
  • Every packet retains SYNTHETIC_NULL_SINK and the non-operational public boundary.

Operator workflow

  1. Copy the template for the exercised dimension.
  2. Run the real task in the actual environment.
  3. Store only bounded, redacted evidence files and record their SHA-256 digests.
  4. Complete every required check and residual unknown.
  5. Run python scripts/verify_acceptance_packet.py PACKET.json.
  6. Preserve executed but unreviewed evidence with python scripts/collect_acceptance_candidate.py PACKET.json --append-candidate.
  7. After explicit human review, create a reviewed successor packet and use python scripts/collect_acceptance_packet.py PACKET.json --reviewed --append.
  8. Neither collector changes release-promotion state automatically.

Contract proof

  • AEP-INV-01 — PASS — Nine independent acceptance dimensions are defined
  • AEP-INV-02 — PASS — Every dimension has required checks
  • AEP-INV-03 — PASS — All blank templates validate deterministically
  • AEP-INV-04 — PASS — Blank templates remain NOT_RUN and unreviewed
  • AEP-INV-05 — PASS — Digest tampering is rejected
  • AEP-INV-06 — PASS — Credential-bearing evidence is rejected without persistence
  • AEP-INV-07 — PASS — Operational fields are rejected
  • AEP-INV-08 — PASS — Automatic promotion is rejected
  • AEP-INV-09 — PASS — Executed checks must reference evidence
  • AEP-INV-10 — PASS — PASS requires human review
  • AEP-INV-11 — PASS — A valid digest is not represented as factual accuracy
  • AEP-INV-12 — PASS — Public packet verification is non-persistent
  • AEP-INV-13 — PASS — Every packet retains SYNTHETIC_NULL_SINK
  • AEP-INV-14 — PASS — Candidate evidence is separate from reviewed evidence
  • AEP-INV-15 — PASS — Candidate packets cannot be mistaken for completed human review
  • AEP-INV-16 — PASS — Candidate and reviewed indexes cannot auto-promote
  • AEP-INV-17 — PASS — Evidence ledger lineage is internally valid
  • AEP-INV-18 — PASS — Evidence ledger exposes no public persistence
  • AEP-INV-19 — PASS — Candidate evidence is never counted as reviewed evidence
  • AEP-INV-20 — PASS — Packet history is deterministic and non-promoting