DA-07 · LESSON 10

Public claims discipline

KEY DEFINITIONS

Terms used in this lesson

Guardian: A Ducat policy-checking signer that can authorize or reject defined protocol transactions.
FROST: Flexible Round-Optimized Schnorr Threshold signing: a protocol in which a required subset produces one group signature.
DKG: Distributed key generation: participants create shares of a group key without one party learning the complete secret.

Marketing language must be traceable to current evidence and must not promote planned decentralization or undeployed fixes as live behavior.

45 min Difficulty 5/5 Not started

VISUAL MODEL

See the whole mechanism before going step by step

Use the diagrams to orient yourself. Then the guided explanation below teaches every part in depth.

4 explanatory views

CONCEPT-SPECIFIC MAP · ducat vaultA Ducat action moves one Bitcoin-anchored vault state to a successorSelect any state to inspect its exact role.

RELATIONSHIP MAPInputs, rule, and outputs

01
PREDECESSORCurrent vault outpoint
The current Bitcoin output anchors collateral and identifies the state being spent.
02
REQUESTPublic claims discipline
The Public claims discipline workflow proposes one exact action and successor state.
03
POLICYProfile, oracle, signatures
Applicable policy, price evidence, authorization, and transaction shape are checked.
04
BITCOIN SPENDScript-valid transaction
Bitcoin miners and nodes can include only a transaction that satisfies Bitcoin rules.
05
SUCCESSORNew outpoint and state
Ducat validators reconstruct debt, collateral, token, and account changes from the confirmed transaction.

Rule shown: Bitcoin checks the spend; Ducat components independently reconstruct and validate the additional protocol state.

STAGE 1 OF 5PREDECESSOR: Current vault outpoint

The current Bitcoin output anchors collateral and identifies the state being spent.

Governing relationship: Bitcoin checks the spend; Ducat components independently reconstruct and validate the additional protocol state. Complete path: 1. PREDECESSOR, Current vault outpoint. The current Bitcoin output anchors collateral and identifies the state being spent. 2. REQUEST, Public claims discipline. The Public claims discipline workflow proposes one exact action and successor state. 3. POLICY, Profile, oracle, signatures. Applicable policy, price evidence, authorization, and transaction shape are checked. 4. BITCOIN SPEND, Script-valid transaction. Bitcoin miners and nodes can include only a transaction that satisfies Bitcoin rules. 5. SUCCESSOR, New outpoint and state. Ducat validators reconstruct debt, collateral, token, and account changes from the confirmed transaction.

1. State transitionWhat exists, what changes, and what results

BEFORE

Draft claim: Ducat uses a decentralized Guardian quorum in production. Supplied evidence shows FROST and DKG implementation at named commits plus a dated technical-session de…

MECHANISM

Name component, behavior, version, environment, date, and status without universal language.

AFTER

Original prose does not turn an internal or disputed fact into a publishable one. Publish only the narrow implementation claim whose evidence and visibility are approved.

Text equivalent: Starting from Draft claim: Ducat uses a decentralized Guardian quorum in production. Supplied evidence shows FROST and DKG implementation at named commits plus a dated technical-session description. It does not establish the current… The mechanism begins when Name component, behavior, version, environment, date, and status without universal language. The resulting lesson is Original prose does not turn an internal or disputed fact into a publishable one. Publish only the narrow implementation claim whose evidence and visibility are approved.

2. Mechanism pathSelect a stage to inspect its job

STAGE 1 OF 4

Write the narrow claim

Name component, behavior, version, environment, date, and status without universal language.

Complete path: 1. Write the narrow claim: Name component, behavior, version, environment, date, and status without universal language. 2. Attach resolving evidence: Link the claim to the exact code, test, deployment observation, configuration, or review that supports it. 3. Check visibility and derivation: Do not publish private source locations, internal claims, or content derived from them when the export policy forbids it. 4. Quarantine conflict: If marketing, repository documentation, code, or deployment disagree, show the uncertainty internally and withhold the stronger public claim.

3. Rule and failure boundaryWhat accepts the result and where it can stop

ACCEPTED PATH

The worked case executes the named inputs and checks in the displayed order. If marketing, repository documentation, code, or deployment disagree, show the uncertainty internally and withhold the stronger public claim.

CHANGED CONDITION

A missing, malformed, stale, unauthorized, or inconsistent required input stops at its first named boundary. Original expression avoids copying, but factual technical and commercial claims still need evidence and accurate status.

Important distinction: Original wording needs no evidence because it is not copied from a source. Original expression avoids copying, but factual technical and commercial claims still need evidence and accurate status.

Text equivalent: The accepted path is enforced by The worked case executes the named inputs and checks in the displayed order. If marketing, repository documentation, code, or deployment disagree, show the uncertainty internally and withhold the stronger public claim. If the required condition changes, A missing, malformed, stale, unauthorized, or inconsistent required input stops at its first named boundary. Original expression avoids copying, but factual technical and commercial claims still need evidence and accurate status.

Loading lesson visuals...

Learn the idea

A public claim is a factual statement shown outside the private learning environment. It should be traceable to dated evidence and use status words precisely. Implemented means code exists at a named revision. Tested names the cases run. Deployed identifies a dated running artifact and environment. Disputed means credible sources conflict. Quarantined means the stronger wording is withheld until the conflict or evidence gap is resolved. Original wording still needs factual support.

GUIDED EXPLANATION1/4 ideas inspected

Write the narrow claim

Name component, behavior, version, environment, date, and status without universal language.

The worked example follows the explanation

Inspect every idea above to open it.

Important distinction“Original wording needs no evidence because it is not copied from a source.”

Original expression avoids copying, but factual technical and commercial claims still need evidence and accurate status.

FINISH LEARNING FIRST

The questions unlock after every required learning activity

Inspect every guided idea, open the worked example, rebuild its mechanism, and complete the deterministic lesson tool. Your progress is saved automatically.