A bare .feature corpus can be imported

spec:carrier.sdp-import.feature-adapter

Use Case / Behavior · storyidea floor idea

Next rung scoped waits on 1 unmet clause:

kind-evidence-present · The kind's natural evidence is present (per-kind evidence table).

Design: no design entries · no pinned declarations · no decisions

specs/carrier/sdp-import.feature-adapter.sdp.md

1 open question and 1 blocking question; implementation binding none, verifier binding none, and expected-outcome oracle none.

Intent

outcome: Convert a bare .feature source corpus into canonical Protocol carriers without adding a second extraction path.

Open questions

blocking · question.featureAdapter line 15 · specs/carrier/sdp-import.feature-adapter.sdp.md:15 · Which bare .feature constructs can an import adapter preserve honestly?Decider: ownerTrigger: an adopter migrates a gen-1 .feature corpus into the Protocol

Verification

Verifier bindings

No verifier binding recorded.

Design view

Requirement drawing

Declared verifying examples: no declared verifying example.
Satisfying or referencing units: no recorded binding.
Test or oracle bindings: no recorded binding.

Requirement drawing for spec:carrier.sdp-import.feature-adapter

Arrows: refines (declared).

The diagram as text

spec:carrier.sdp-import.feature-adapter: A bare .feature corpus can be imported · declared Spec · no satisfying binding
spec:carrier.sdp-import: A TypeScript-carried Spec can be converted to Markdown · declared Spec
spec:carrier.sdp-import.feature-adapter refines spec:carrier.sdp-import · declared

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred and chosen syntax: requirementDiagram; exact refines, satisfies and verifies, with claim words in nodes and per-edge comments.

Mermaid source for Requirement drawing for spec:carrier.sdp-import.feature-adapter

requirementDiagram
  requirement n0 {
    text: "A bare .feature corpus can be imported · declared Spec · no satisfying binding · spec:carrier.sdp-import.feature-adapter"
  }
  requirement n1 {
    text: "A TypeScript-carried Spec can be converted to Markdown · declared Spec · spec:carrier.sdp-import"
  }
  %% claim: declared
  n0 - refines -> n1

Decisions

No decision record named.

Runtime

No implementation neighborhood recorded.

Runtime observation: not tracked.

Evidence

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.

Impact

Relations of spec:carrier.sdp-import.feature-adapter

Arrows: refines (declared).

The diagram as text

spec:carrier.sdp-import: A TypeScript-carried Spec can be converted to Markdown
spec:carrier.sdp-import.feature-adapter: A bare .feature corpus can be imported
spec:carrier.sdp-import.feature-adapter refines spec:carrier.sdp-import · declared

Mermaid source

Copyable source; the Studio draws static SVG.

Preferred syntax: flowchart. Chosen syntax: labelled flowchart, preserving exact relations, claims and folds.

Mermaid source for Relations of spec:carrier.sdp-import.feature-adapter

flowchart TB
  n0["A TypeScript-carried Spec can be converted to Markdown · spec:carrier.sdp-import"]
  n1["A bare .feature corpus can be imported · spec:carrier.sdp-import.feature-adapter"]
  n1 -->|"refines · declared"| n0

Rests on

refines · spec:carrier.sdp-import · stated ready, floor ready

Rested on by

No Spec rests on this Spec.

Relations

Relation and direction	Other end	Claim	Reason	Exercised keys
refines · outgoing	A TypeScript-carried Spec can be converted to Markdown `spec:carrier.sdp-import` · resolves	declared	None	None

Bindings

Implementation binding: none

Design reference: none

Verifier binding: none

Expected-outcome oracle: none

Runtime observation: not tracked.

Run results: not recorded in the graph.

Findings

None.

Composing (0)

Composing needs the script.