Advisory demo - you be the judge
Can a system score something as "perfect"... even when it clearly isn't?
Explore how DBaD signals can be interpreted into an advisory score. The score is not truth. You decide what it means.
You don't need to understand this. Just click around.
Start with a scenario, then compare how different advisory profiles read the same visible DBaD trace. This page is running presentation hardening v0.3.2 over DecencyMeter v0.1 baseline and experimental v0.2 score models.
100-100
Advisory Score Range
Interpretation varies by profile.
Start here - choose a scenario
These are demonstration cases. They are not real-world events.
Audit Case
A realistic, mixed-quality response
See how documented trade-offs and limits are interpreted.
Open audit case Stress caseStress Case
Multiple red flags and missing data
See how severe issues and omissions affect the advisory score.
Open stress case Synthetic anomaly"Perfect" Incident
This one scores 100... but feels wrong.
A synthetic anomaly designed to challenge your intuition.
Open perfect incidentThese are demonstration cases. They are not real-world events.
Quick access
Jump directly to the adjacent critique and context surfaces without hunting through the nav.
Important Boundary Notice
These warnings still lead the interpretation. The layout is friendlier now, but the boundaries did not get softer.
Not DBaD validation
DBaD validates structure, not ethics or truth.
Not proof of truth
This does not prove correctness, truth, or ethical behavior.
Interpretation of signals
This is an interpretation of recorded signals, not a factual verdict.
Profiles are advisory
Profiles are lenses over the same trace, not protocol changes.
Experimental v0.2
Experimental v0.2 is experimental and not DBaD validation.
No proof of goodness
v0.2 does not prove truth, safety, goodness, or correctness.
Framework and Version Alignment
API and framework boundary: DBaD emits the trace and validation context; DecencyMeter interprets that trace downstream; the v0.3.x layer constrains how the score is presented.
DBaD v2.2 runtime framework
DBaD validates trace structure and recorded integrity signals. It does not score ethics, truth, goodness, or real-world outcomes.
DecencyMeter v0.1 baseline score model
The current deterministic advisory score model shown on this page.
DecencyMeter experimental v0.2 score model remains a comparison layer only: A side-by-side comparison model that adds outcome-aware caution signals without changing DBaD validation.
Presentation hardening v0.3.2
This page binds warning hierarchy, profile, version, case context, and portable citation directly to every public score surface.
If you quote this, include this.
Portable Citation Object: Portable citation object: a reusable advisory notice designed to travel with screenshots, quotes, press references, decks, emails, and regulator or journalist excerpts. It is not a legal disclaimer or enforcement tool; it is a presentation-discipline tool that makes omission of context visibly dishonest.
Short Notice
DecencyMeter Advisory Notice: Advisory only. Not DBaD validation. Not proof of ethical behavior, truth, or outcome quality. Profile, version, and context matter.
Current Surface Notice
DecencyMeter Advisory Notice: This synthetic pressure-test output is advisory only. It is not DBaD validation and not proof of ethical behavior, truth, or real-world outcome quality. Profile, version, and case context matter.
Experimental Notice
DecencyMeter Advisory Notice: This synthetic pressure-test output and experimental DecencyMeter output are advisory only. They are not DBaD validation and not proof of ethical behavior, truth, or real-world outcome quality. Profile, version, and case context matter.
Observation Check
System is now in observation phase. Use these lightweight links to flag interpretation reactions without changing scoring, DBaD validation, or stored traces.
Profile Selector
Choose a visible advisory scoring profile for the selected trace case. Missing or invalid profile values default to baseline.
Active case
Perfect-looking incident trace
A synthetic pressure-test trace that is procedurally clean, still records an incident outcome, and exists to make the scoring anomaly directly inspectable.
This is a synthetic pressure-test trace, not real-world evidence, and not a DBaD failure. It exists to show how a procedurally clean incident can behave under v0.1 and experimental v0.2 scoring.
Selected profile
Strict Audit
Profile key: strict_audit
Heavier procedural deductions for evidence, completeness, blind spots, and escalation closure drift.
Score Models: v0.1 Baseline vs Experimental v0.2
This comparison keeps DecencyMeter v0.1 baseline score model visible as the current score model and adds DecencyMeter experimental v0.2 score model as a side-by-side downstream comparison only.
Direct-link boundary: every score card below carries its own advisory context so it can still resist overread when linked or screenshotted on its own.
Quote rule: copy one of the portable citation notices above rather than quoting a selected score by itself.
Before/after delta: -28 points for the selected case/profile.
DecencyMeter v0.1 baseline score model
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Advisory only. Not DBaD validation. Not proof of ethical behavior, truth, or outcome quality.
Visible profile range: 100-100/100
Profile: strict_audit (current baseline)
Case: Perfect-looking incident trace / synthetic pressure test
Synthetic pressure test. Not real-world evidence.
Selected score: 100/100
Total deductions: 0
DecencyMeter experimental v0.2 score model
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Advisory only. Not DBaD validation. Not proof of ethical behavior, truth, or outcome quality.
Visible profile range: 100-100/100
Profile: strict_audit (experimental comparison)
Case: Perfect-looking incident trace / synthetic pressure test
Experimental comparison only. Synthetic pressure test. Not real-world evidence.
Selected score: 72/100
Before/after delta: -28
New v0.2-only deductions: 28
Experimental v0.2 is not DBaD validation. It is a transparent comparison model informed by the documented perfect-looking incident trace anomaly.
The perfect-looking incident trace `trc_20260428193300_pf67c1e2` motivated this experimental comparison and remains documented in the pressure-test results.
Read the scoring anomaly explainer for the public explanation of why v0.2 exists and why the issue belongs to DecencyMeter rather than DBaD. The broader synthetic suite is also available in the pressure-test catalogue.
Profile Comparison (Baseline Score Model)
Profile comparison shows different advisory interpretations over the same DBaD trace under DecencyMeter v0.1 baseline score model. It is not DBaD validation.
Visible range: 100 to 100 with spread 0. The highest score is shown only as part of the range, not as the dominant claim.
Portable citation rule: quote the range and advisory notice first; selected profile scores are supporting detail only.
| Profile name | Score | Total deductions | Triggered deduction count | View |
|---|---|---|---|---|
| Baseline |
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Visible profile range:
100-100/100Profile:
baselineCase: Perfect-looking incident trace / synthetic pressure test
Synthetic pressure test.
Selected score:
100/100 |
0 | 0 | View profile |
| Strict Audit selected |
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Visible profile range:
100-100/100Profile:
strict_auditCase: Perfect-looking incident trace / synthetic pressure test
Synthetic pressure test.
Selected score:
100/100 |
0 | 0 | View profile |
| Operational Tolerance |
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Visible profile range:
100-100/100Profile:
operational_toleranceCase: Perfect-looking incident trace / synthetic pressure test
Synthetic pressure test.
Selected score:
100/100 |
0 | 0 | View profile |
| Humanitarian / Common Sense |
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Visible profile range:
100-100/100Profile:
humanitarian_common_senseCase: Perfect-looking incident trace / synthetic pressure test
Synthetic pressure test.
Selected score:
100/100 |
0 | 0 | View profile |
| Experimental |
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
Visible profile range:
100-100/100Profile:
experimentalCase: Perfect-looking incident trace / synthetic pressure test
Synthetic pressure test.
Selected score:
100/100 |
0 | 0 | View profile |
Why profiles differ
- Each profile applies different visible weights to the same recorded DBaD signals.
- A strict audit profile penalizes missing evidence and unresolved governance signals more heavily.
- An operational tolerance profile penalizes the same signals less heavily.
- A humanitarian/common-sense profile weighs unresolved harm-facing or closure signals more heavily.
- The experimental profile exists to test alternative interpretations, not to define the default.
Profile differences are interpretive differences, not DBaD validation differences.
Inputs Used
These are the visible DBaD fields used by this first deterministic advisory model.
validation result
Value: valid
Field: validation.is_valid
Trace passed deterministic DBaD validation.
expected_outcome vs outcome_status
Value: incident vs incident
Field: expected_outcome.label / outcome_status
No mismatch in this audited trace.
declared_blind_spots
Value: 0 total / 0 open
Field: declared_blind_spots[]
Only open blind spots trigger deductions in this demo model.
state_transition_evidence presence
Value: recorded
Field: transition_history[].state_transition_evidence
Missing evidence advisory notes trigger a deduction even if another transition has evidence.
escalation_closure status
Value: not recorded (not_applicable)
Field: escalation_closure / escalation_closure_status
This demo model only deducts when escalation context exists and closure is not approved_to_continue.
completeness_attestation
Value: declared_complete
Field: completeness_attestation.status
Anything other than declared_complete triggers a deduction in this demo model.
outcome_status
Value: incident
Field: outcome_status
Displayed as a visible downstream signal, not as truth or correctness.
trace_version/history depth
Value: v13 / 5 history entries
Field: trace_version / history arrays
Shown for context only in this first demo. No deduction is attached.
Simple Scoring Model
This demo uses a transparent, deterministic rule sheet for the selected advisory profile. No ML. No hidden weights.
Model start
Start at: 100
Every deduction below is visible and rule-based.
expected_outcome mismatch
Deduction: -25
Subtract when expected_outcome and outcome_status differ after outcome is known.
missing evidence
Deduction: -15
Subtract when a supported transition is missing recorded state_transition_evidence.
open blind spots
Deduction: -8
Subtract the listed amount for each declared blind spot still marked open.
completeness not declared_complete
Deduction: -15
Subtract when completeness_attestation.status is not declared_complete.
escalation closure not approved_to_continue
Deduction: -20
Subtract when escalation context exists and disposition is not approved_to_continue.
Experimental v0.2 Additions
These are the new visible experimental v0.2 deductions added on top of the current v0.1 baseline. The perfect-looking incident trace is now a public selector case so the anomaly can be inspected directly.
outcome status incident
Deduction: -18
Subtract when outcome_status is incident, even if the surrounding process is otherwise clean.
outcome status reversed
Deduction: -20
Subtract when outcome_status is reversed.
outcome status escalated
Deduction: -12
Subtract when outcome_status is escalated.
incident plus approved_to_continue caution
Deduction: -12
Subtract when an incident outcome coexists with escalation closure approved_to_continue.
incident plus no-blind-spots confidence caution
Deduction: -10
Subtract when an incident outcome coexists with no blind spots and declared_complete completeness.
over-verification / minimal-evidence caution
Deduction: -8
Subtract when verification history is heavy while a supported transition still lacks evidence.
Score (Baseline Score Model v0.1)
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
DecencyMeter Advisory Notice: This synthetic pressure-test output is advisory only. It is not DBaD validation and not proof of ethical behavior, truth, or real-world outcome quality. Profile, version, and case context matter.
Visible profile range: 100-100/100
Selected profile: Strict Audit
Case: Perfect-looking incident trace / synthetic pressure test
Active trace: trc_20260428193300_pf67c1e2. Synthetic pressure test, not real-world evidence.
Selected score: 100/100
No deductions were triggered by this first advisory rule set.
Score (Experimental v0.2 Comparison Model)
ADVISORY ONLY — NOT DBaD VALIDATION — NOT PROOF OF ETHICAL BEHAVIOR
DecencyMeter Advisory Notice: This synthetic pressure-test output and experimental DecencyMeter output are advisory only. They are not DBaD validation and not proof of ethical behavior, truth, or real-world outcome quality. Profile, version, and case context matter.
Visible profile range: 100-100/100
Selected profile: Strict Audit
Case: Perfect-looking incident trace / synthetic pressure test
Experimental comparison only. Synthetic pressure test, not real-world evidence.
Selected score: 72/100
Before/after delta: -28
- -18 Observed outcome status is `incident`, which the experimental model treats as a direct downstream caution signal.
- -10 An incident outcome coexists with zero declared blind spots and `declared_complete` completeness, so v0.2 reduces the score to avoid a perfect-looking incident result.
Experimental v0.2 is experimental. It does not prove truth, safety, goodness, or correctness.
Explainability (Baseline Score Model v0.1)
Every deduction shows the triggering signal and the DBaD field it came from.
No deductions were triggered, so this section is empty for the audited trace under the current rule sheet.
Experimental v0.2 Explainability
These are the exact new v0.2-only deductions and the recorded DBaD fields they came from. This is not DBaD validation.
outcome status incident
What triggered it: Observed outcome status is `incident`, which the experimental model treats as a direct downstream caution signal.
DBaD field: outcome_status
Deduction: -18
Experimental v0.2 is not DBaD validation. It is a downstream comparison model only.
incident plus no-blind-spots confidence caution
What triggered it: An incident outcome coexists with zero declared blind spots and `declared_complete` completeness, so v0.2 reduces the score to avoid a perfect-looking incident result.
DBaD field: outcome_status / declared_blind_spots / completeness_attestation.status
Deduction: -10
Experimental v0.2 is not DBaD validation. It is a downstream comparison model only.
Challenge this score
This score is based on explicit weights and recorded trace signals.
You are encouraged to challenge the assumptions, weights, and interpretation.
Current weights
mismatch→-25missing_evidence→-15open_blind_spot_each→-8 eachcompleteness_not_declared→-15escalation_not_approved→-20
Submit a scoring critique
A disagreement with this score does not invalidate DBaD validation.
Experimental v0.2 Comparison Weights
Visible v0.2 comparison weights only. No hidden scoring. No database writes.
outcome_status_incident→-18outcome_status_reversed→-20outcome_status_escalated→-12incident_approved_to_continue→-12incident_no_blind_spots_declared_complete→-10over_verified_minimal_evidence→-8
Trace Context
Validation result
valid
Trace passed deterministic DBaD validation.
Advisory notes
none
Violations
none
Links Back
v2.2 demo · Top issues · DecencyMeter bridge · Scoring anomalies · Pressure tests · Try to break DBaD