A structured decision grid for proposals, criteria, evidence and AI-backed verdicts.
The project is a source-backed GenLayer workflow, with frontend views designed around evidence status rather than generic contract buttons.
DecisionGrid V2 (# v0.2.16), schema-valid strong lifecycle contract with JSON-backed cases/evidence/reviews/challenges/appeals/audits/profiles, GenLayer web render + prompt-comparative reasoning, legacy frontend wrappers and reputation scoring.
The important files are:
contracts/decisiongrid_v2.py- GenLayer contract sourcedeployment.json- Studionet address, deploy transaction and smoke transaction hashespackage.json- frontend runtimeREADME.md- this operator and reviewer guide
- Network: studionet (61999)
- Contract: 0x6C99F053faCBbF10A1D00a52a5bC3D4571c3764d
- Deploy tx: 0xb5e68fb3...e825cd
- Deployed at: 2026-06-24T17:11:59.355Z
- Smoke writes recorded: 13
Typical flow: create_case -> open_challenge_window -> submit_challenge -> review_with_genlayer -> resolve_challenge_with_genlayer -> submit_appeal -> archive_case
Useful reads: get_case_count, get_case, get_case_record, get_evidence, get_reviews, get_challenges, get_appeals, get_audit_log
- Primary source:
contracts/decisiongrid_v2.py(29,783 bytes) - Public write/action methods: 15
- Read methods: 20
- GenLayer features: live web rendering, LLM adjudication, indexed storage, append-only collections
- configure_protocol: 0x70d4ed19...e01202
- create_case: 0x9068a763...e3e855
- add_evidence_web: 0xefd10d30...655f3b
- add_evidence_security: 0x5d162931...b6f62d
- add_evidence_whitepaper: 0x6ce8e166...51a063
- review: 0xf3f0e572...e3308b
- challenge_window: 0x714581cd...42ff15
- submit_challenge: 0xcfdc175f...575980
cd <this-repository-folder>
npm install
npm run devOpen the dev server URL printed by npm.
- Repository: https://github.com/aspro45/bauhaus-decision-grid
- Live app: https://bauhaus-decision-grid.vercel.app
- Framework: Next.js
- Build:
npm run build
-
This repository should contain no decrypted wallet material.
-
The Studionet deployer private key stays in the local encrypted vault.
-
Vercel deployment should use this repository folder only.
-
QA notes: Frontend preview verified through the single Next preview slot. Contract address and smoke txs are registered; private key remains encrypted vault-only.