W3C Decentralized Identifiers
Generated Evaluation Status
This section is generated from the framework manifest and compatibility report. Do not edit it manually.
- Framework ID:
w3c-did - Manifest:
docs/external-frameworks/w3c-did.json - Compatibility report:
./reports/w3c-did.compatibility.json - Evidence class:
SOURCE_REVIEWED - Independently reproducible:
False - Comparative-testing claim allowed:
False - Missing reproducibility gates:
shared_test_vector, raw_output, timestamp, runtime_configuration, source_version_or_hash, replay_commands, declared_expected_outcome, independent_reproduction - Evaluation result:
COMPATIBILITY_EVIDENCE_ONLY - Cycle status:
FIRST_FRAMEWORK_CYCLE_COMPLETE - Execution authority claim:
False - Next bounded action: Add executable observations, raw outputs, pinned versions, replay commands, and independent reproduction before making comparative-testing claims.
- Posting source: generated compatibility report
- Generated status is descriptive compatibility evidence only.
Generated Authored Analysis Boundary
This section is generated. Do not edit it manually.
- Framework ID:
w3c-did - Framework name:
W3C Decentralized Identifiers - Generated sections above this boundary may be rebuilt from registry, manifest, compatibility-report, and result artifacts.
- Authored analysis below this boundary may contain interpretation, notes, and framework-specific discussion.
- Generators must preserve authored analysis unless a future validator explicitly declares a migration path.
- Boundary rule: generated material is descriptive compatibility evidence only and does not create certification, endorsement, adoption, proof, or operational permission.
Generated Transition Mapping
This section is generated from the framework manifest. Do not edit it manually.
| Field | Generated Value |
|---|---|
framework_identity | W3C Decentralized Identifiers |
source_reference | https://w3c.github.io/did/ |
source_version | DID Core editor draft recorded |
allowed_use_boundary | identifier and control evidence only |
claims | decentralized identifiers and DID documents |
non_claims | no delegation or execution authority |
input_artifact_type | DID and DID document |
output_artifact_type | resolved identity and control evidence |
actor_or_authority_model | controller relationship evidence only |
evidence_model | official draft source plus bounded crosswalk |
policy_or_rule_model | DID method and verification rules |
delegation_model | not established |
decision_or_result_model | resolution and verification evidence |
execution_authority_claim | false |
receipt_or_trace_model | DID document and manifest references |
reconstruction_model | DID documents support identity and control reconstruction |
SPE_overlap | identity evidence may inform standing review |
StegVerse_ecosystem_overlap | authority, freshness, and reconstruction boundary |
fail_closed_conditions | missing source status, resolution context, mapping, or authority overclaim |
Generated mapping is compatibility evidence only.
Generated Framework Metadata
This section is generated from the external-framework registry. Do not edit it manually.
- Framework ID:
w3c-did - Name:
W3C Decentralized Identifiers - Registry status:
SOURCED-CROSSWALK-PROVISIONAL - Testbench state:
SOURCE_RECORDED_CROSSWALK_PROVISIONAL - Manifest path:
docs/external-frameworks/w3c-did.json - Source reference:
https://w3c.github.io/did/ - Metadata boundary: generated metadata is descriptive only; it does not create certification, endorsement, formalism adoption, admissibility proof, or execution authority.
Status
Relationship type: external framework crosswalk
Evidence class: SOURCE_REVIEWED
Page completeness: COMPLETE_WITH_EXTERNAL_GATES
Runtime observation: none attached
Independent reproduction: false
Comparative testing claim allowed: false
Execution authority claim allowed: false
Maintenance owner: admissibility-wiki External Frameworks audit
Official Source
- DID Core editor draft: https://w3c.github.io/did/
- Source posture: editor draft captured; draft status is preserved and no resolver or method implementation is selected.
Framework-Native Scope
Decentralized Identifiers define identifiers and DID documents containing verification methods, services, and controller relationships without requiring one centralized identifier registry. Resolution behavior and security properties remain dependent on the selected DID method and implementation.
Evidence Provenance
| Evidence class | Current evidence | Status | Missing fields |
|---|---|---|---|
| Official framework source | W3C editor draft | present with caution | stable recommendation status, immutable source hash |
| Method specification | No DID method selected | missing | method version and security model |
| Implementation source | No resolver pinned | missing | resolver version, configuration, commit |
| Observed behavior | No resolution or proof verification run | missing | DID, document, output, timestamp |
| Reproduced behavior | No independent rerun | missing | replay command, environment, second result |
| StegVerse analysis | Bounded crosswalk | present | method-specific fixture |
Relationship to Admissibility
DID infrastructure asks: What identifier document, verification methods, services, and controller relationships resolve for this identifier?
StegVerse Admissibility asks: Does the current actor hold bounded authority for this action and consequence now?
DID resolution and proof verification can contribute identity and control evidence. They do not independently establish current delegation, action scope, policy validity, or transition admissibility.
Execution Authority Boundary
DID control != universal actor authority
resolution success != current delegation
verification method != permission for every action
identifier persistence != current standing
Observation Boundary
Selected DID method: none
Pinned resolver: none
DID document fixture: none
Verification proof fixture: none
Raw resolution output: none
Timestamp and method snapshot: none
Independent replay: none
No method-specific interoperability result is claimed.
StegVerse Analysis
| Criterion | Current result |
|---|---|
| Identity | A DID may identify a subject or controller within a method-specific trust model. |
| Authority | Controller relationships do not by themselves prove action-level authority. |
| Policy | Method rules, resolver policy, verification-purpose rules, and target policy must be explicit. |
| Delegation | Delegation requires separate evidence tying actor, action, target, and validity window. |
| Evidence | DID documents and proofs can support reconstruction when versions and method state are retained. |
| Replayability | Requires pinned method, resolver, network state, DID document, and proof. |
| Reconstructability | Depends on historical resolution state, method registries, and retained evidence. |
| Commit-time validity | Requires current resolution plus independent authority and policy checks. |
| Failure behavior | Unresolvable, ambiguous, stale, or unverifiable identifiers must fail closed. |
Commit-Time Interoperability Contract
transition_id
did
did_method
did_document_digest
controller_relationships
verification_method
verification_purpose
resolution_result
resolution_timestamp
resolver_version
method_state_reference
policy_reference
delegation_reference
requested_action
target_system
validity_window
Failure Classes
| Failure class | Applies | Notes |
|---|---|---|
| Actor ambiguity | yes | Subject, controller, key holder, and executing actor may differ. |
| Authority drift | yes | Controller and verification-method state may change. |
| Stale evidence | yes | Cached DID documents may no longer be current. |
| Delegation leakage | yes | Identifier control can be overread as broad authority. |
| Replay divergence | yes | Method state or resolver behavior can alter results. |
| Source-claim mismatch | yes | Draft or method-specific behavior may be described too generally. |
Machine-Readable Companions
- Manifest:
docs/external-frameworks/w3c-did.json - Compatibility report:
docs/external-frameworks/reports/w3c-did.compatibility.json - Registry:
docs/external-frameworks/index.json - Canonical inventory:
static/external-frameworks/canonical-union-inventory.v1.json
Validation Completion Criteria
select one DID method and pin its specification
pin one resolver implementation and state source
publish a DID document and proof fixture
capture raw resolution and verification output with timestamp
publish replay commands and expected result
complete an independent rerun
route identity evidence into a Commitment Candidate without inheriting authority
Non-Claims
DIDs are not a StegVerse canonical formalism. Identifier control and resolution success are not current delegation, transition admissibility, execution authority, certification, or general compatibility. This page does not treat the editor draft as a final recommendation.
Challenge Path
A challenge must identify the DID method, resolver, document version, controller or proof claim, supporting evidence, and requested correction. Method-specific evidence cannot be generalized silently.
Next Safe Build Target
Publish one pinned DID-method resolution and proof-verification fixture with raw output, historical state references, immutable hashes, replay instructions, and an independent rerun.
This page reflects a bounded admissibility packet. Publication does not create standing.