FAQ

Short answers to the questions most likely to come from skeptical or confused first-time readers of the current DBaD public baseline.

Is this just another AI ethics framework?

No. DBaD is now positioned as a governance protocol for trust over time, not just a framework for labeling one output.

What does DBaD actually enforce?

It enforces a narrow set of trust constraints around continuity, verification independence, trajectory, and lineage visibility. The goal is to control unsafe trust propagation, not to solve every governance problem.

Why does DBaD sometimes allow an action even when concerns are still triggered?

Because DBaD separates constraints that block action from concerns that remain visible for audit and review. Not every concern prevents action. When action is still allowed, the system keeps those concerns visible on purpose rather than hiding them.

What does DBaD not solve?

It does not fully solve cross-chain coordination, hidden collusion, substantive verifier capture, or global intent reconstruction. Those limits are documented openly as boundary conditions.

Can this be gamed?

Yes. DBaD assumes adversarial behavior. Its job is to make harmful trust movement harder to hide and easier to audit, not to eliminate all attacks.

Why should anyone trust this?

Because it is presented as a tested public draft baseline with known flaws, known limits, and visible revisions. The project is stronger when it shows what it can and cannot prove.

How is this different from a scoring model?

A scoring model evaluates one action. DBaD is about what happens after that: whether trust continues, where it should stop, and what the trace must preserve.

Is this production-ready?

Not as a finished governance product. The public site presents a public draft baseline, a working evaluator demo, and a tested architectural direction.

What is the difference between this site and Decency Meter?

ethics.decencymeter.com is the DBaD research and governance surface. decencymeter.com is the lighter public-facing pulse-check built on top of that broader work.

Where should I go next if I want the real system story?

Start with DBaD Explained, then read White paper v3, review known limits, and use the research demo as a partial prototype.