Skip to content

assmore22/incidentdeck

Repository files navigation

IncidentDeck

Live Links

The project is packaged as a real protocol surface, not a placeholder page: the contract stores records, exposes read models and records smoke-tested writes.

IncidentDeck Brief

8 record types (Incident/Evidence/TimelineEvent/Remediation/Challenge/Appeal/Reputation/AuditEntry) across DynArray[str] stores + TreeMap reputations + TreeMap status/severity/reporter indexes + recent_ids + u256 clock; 16 write + 20 view methods; 9-state incident lifecycle DRAFT->OPEN->TRIAGED->ROOT_CAUSE_PROPOSED->REMEDIATION_REVIEW->CHALLENGE_WINDOW->APPEALED->FINALIZED->ARCHIVED; nondet reasoning via gl.nondet.web.render + gl.nondet.exec_prompt inside gl.eq_principle.prompt_comparative for root-cause review (with per-evidence credibility + injection risk + timeline-consistency), remediation review (completeness/regression bps), and challenge/appeal adjudication; confidence + reputation in basis points (0-10000); strict-JSON prompt-injection defenses with INVALID_REASONING_JSON safe fallback; finalized incidents immutable except archive; every write appends an audit entry.

The important files are:

  • contracts/IncidentDeck.py - GenLayer contract source
  • deployment.json - Studionet address, deploy transaction and smoke transaction hashes
  • package.json - frontend runtime
  • README.md - this operator and reviewer guide

Contract Receipt

Protocol Mechanics

Typical flow: create_incident -> open_triage -> submit_remediation -> review_root_cause_with_genlayer -> resolve_challenge_with_genlayer -> open_challenge_window -> submit_appeal -> archive_incident

Useful reads: get_incident, get_incident_count, get_recent_incidents, get_incidents_by_reporter, get_incidents_by_status, get_incidents_by_severity, get_evidence, get_incident_evidence

  • Primary source: contracts/IncidentDeck.py (52,390 bytes)
  • Public write/action methods: 16
  • Read methods: 20
  • GenLayer features: live web rendering, LLM adjudication, validator-comparative consensus, indexed storage, append-only collections

Smoke Trail

Inspect The App

cd <this-repository-folder>
npm install
npm run dev

Open the dev server URL printed by npm.

Security Notes

  • This repository should contain no decrypted wallet material.

  • The Studionet deployer private key stays in the local encrypted vault.

  • Vercel deployment should use the project folder only.

  • QA notes: Browser QA 1440px + 390px: operations timeline room (ultra-thin status bar; left incident switcher with 5 seeded incidents across DRAFT/OPEN/TRIAGED/ROOT_CAUSE_PROPOSED/CHALLENGE_WINDOW/ARCHIVED states...

About

Incident review and remediation protocol with evidence timelines, root-cause review, appeals, and GenLayer consensus.

Topics

Resources

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

No releases published

Packages

 
 
 

Contributors