109-impact-and-conflict-are-declared

Impact and conflict are declared

Lifecycle approvedImplementation completeVerification unknownQualification unknown

A spec can say which specs it extends and amends. It cannot say which requirements it is expected to affect, or which requirements it knowingly conflicts with. Both are declared in frontmatter against spec 106's qualified obligation ids, validated at compile, carried in the registry, and answered by one read that inverts the declarations so the affected side can see them. Nothing gates on either, and nothing computes an impact.

Read the full pinned specification ↗

Relationships

depends on

106-obligations-are-declared-constraints

Claimed units

establishes

{
  "kind": "file",
  "path": "crates/spec-spine-types/src/impact.rs"
}

establishes

{
  "kind": "file",
  "path": "crates/spec-spine-core/src/impact.rs"
}

establishes

{
  "kind": "file",
  "path": "crates/spec-spine-core/tests/impacts.rs"
}

establishes

{
  "kind": "file",
  "path": "crates/spec-spine-cli/tests/impacts.rs"
}

extends

{
  "nature": "additive",
  "spec": "000-spec-spine-bootstrap",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/src/frontmatter.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/src/registry.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/src/lib.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/src/version.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/schemas/registry.schema.json"
  }
}

extends

{
  "nature": "additive",
  "spec": "022-index-sharding",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/schemas/registry-spec-shard.schema.json"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/compile.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "003-conformance-lint",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/lint.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "001-compile-registry",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/src/lib.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "002-registry-query",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-cli/src/cmd_registry.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "022-index-sharding",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-types/tests/dtos.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "074-a-governed-read-names-its-version",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/read.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "106-obligations-are-declared-constraints",
  "unit": {
    "kind": "file",
    "path": "crates/spec-spine-core/tests/obligations.rs"
  }
}

extends

{
  "nature": "additive",
  "spec": "088-the-template-teaches-the-whole-grammar",
  "unit": {
    "kind": "file",
    "path": "standards/spec/templates/spec-template.md"
  }
}

extends

{
  "nature": "additive",
  "spec": "057-the-docs-name-what-adopters-derived",
  "unit": {
    "kind": "file",
    "path": "docs/schema-versioning.md"
  }
}

extends

{
  "nature": "additive",
  "spec": "057-the-docs-name-what-adopters-derived",
  "unit": {
    "kind": "file",
    "path": "docs/api.md"
  }
}

extends

{
  "nature": "corrective",
  "spec": "103-a-verifier-fixture-is-a-published-artifact",
  "unit": {
    "kind": "directory",
    "path": "crates/spec-spine-core/fixtures/verifier/"
  }
}

Source headings

109: Impact and conflict are declared
1. Purpose
1.1 Why the obligations dependency is real
1.2 What it enables (D-1)
2. Territory
3. Behavior
3.1 Two declarations, in frontmatter
3.2 An impact names an obligation, qualified and resolving
3.3 A conflict is declared, not resolved
3.4 Validation at compile
3.5 What these establish, and what they do not
3.6 The read inverts the declarations
3.7 The registry and the versions
3.8 Nothing gates on either
4. Out of scope
5. Resolved decisions
Verification

Frozen anchors

No frozen anchors declared.