Spec Studio

Open questions

Recipe 20, the open-question register.

  • 16 open questions.
  • 10 blocking questions.
  • 6 non-blocking questions.
  • 6 deferrals.
  • 4 blocking questions without a trigger.
  • 12 Specs with questions.
  • 9 Specs with blocking questions.
  • 0 malformed entries.
16 of 16 shown

A bare .feature corpus can be imported · idea

spec:carrier.sdp-import.feature-adapter

  • blocking · deferral · question.featureAdapter · Which bare .feature constructs can an import adapter preserve honestly?Decider: ownerTrigger: an adopter migrates a gen-1 .feature corpus into the Protocol

Exhaustive symbol reach waits for a language-neutral identity · idea

spec:consumers.impact-graph.symbol-reach

  • blocking · deferral · question.symbolIdentity · Which language-neutral identity and extraction boundary can support exhaustive symbol reach without freezing a single compiler's representation into the Protocol?Decider: ownerTrigger: a reader needs symbol-level reach that file-level imports and curated anchors cannot give

Roadmap views read releases, baselines and phases from git and the graph · scoped

spec:consumers.projections-model.roadmap-views

  • blocking · deferral · question.releaseReader · Does a reader need release or baseline views that the roadmap, the recipes and git tags do not serve?Decider: ownerProvisional: Keep release and baseline views deferred; the trigger opens this question and does not authorize either view's build.Trigger: the first published release

A reference projection serves a reader outside the repository · idea

spec:consumers.reference-projection

  • blocking · deferral · question.namedOutsideReader · Does a human reader outside the repository need a reference projection the four shipped roots do not serve? The taxonomy row is not that reader.Decider: ownerTrigger: a named consumer outside the repository, with a way to measure that demand inside the arc that builds the projection
  • non-blocking · question.referenceSource · Would the reference read pinned declarations, contract-kind Specs or api: code anchors, and does any of them hold enough to document an interface?

A pinned declaration shows the words of each test line that cites it · scoped

spec:consumers.spec-studio.cited-line-text

  • blocking · question.lineText · May the Studio show source text the graph does not hold, and if so is it recorded in the graph beside the citation or read as a named input?Decider: ownerProvisional: the extractor records the citing line's text, trimmed and bounded, on the citation row it already writes, as inferred data that confers nothing, and the Studio reads no source
  • non-blocking · question.lineBound · How long may a recorded line be, and how does a page show a line that was cut?Decider: delegatedProvisional: a bound of a few hundred code units, cut at a word boundary and marked as cut, the whole line one source link away

An outside register is a named Studio input, so a cited token links to its entry · scoped

spec:consumers.spec-studio.register-input

  • blocking · question.registerEntry · What does a register file give the Studio beyond what the external-registers recipe reads, so a token's entry can be shown?Decider: delegatedProvisional: an optional title and an optional href on a token object; the Studio writes one page per register listing each token with its title, retired tokens marked, each linking to its href when present
  • blocking · question.inputForm · How does the studio verb name a register, its pattern and the words that name it on a page?Decider: delegatedProvisional: a repeatable --register NAME=PATH with a matching --register-pattern NAME=SOURCE, the name naming the register in words wherever it shows
  • non-blocking · question.textLinks · Does a cited token become a link inside the rendered text of a Spec, or only in a list beside it?Decider: delegatedProvisional: inside the text, matched by the register's pattern exactly as the recipe matches it, so the page and the check agree on what is cited

Mermaid diagrams can be rooted at code units · scoped

spec:consumers.structural-mermaid

  • blocking · deferral · question.namedStructuralReader · Does a reader need diagrams rooted at code units, which census tables and Spec-rooted one-hop Mermaid do not serve?Decider: ownerTrigger: a named reader with that need, plus a decision that refines spec:decisions.shipped-projections-frozen for the affected Mermaid rendering or supersedes that ruling whole

Runtime observations can close the liveness loop · idea

spec:observation.runtime-overlay

  • blocking · deferral · question.observationIdentity · Which external observation identity and freshness boundary is small enough for the graph while still supporting an honest observed delivery fact?Decider: ownerTrigger: An adopter needs runtime measurements linked to measurable Spec targets and can supply an observation identity and freshness policy for review.

The Protocol removes its frozen plans, review reports and superseded concept material · idea

spec:protocol.delivery-record-cleanup

  • blocking · question.durableContent · Which content in plans/, reviews/ and the concept documents does no Spec, test, decision or recipe carry yet, and where does each piece belong?Decider: ownerProvisional: a measured inventory by the arc that removes them, reviewed before anything is deleted

A slice page shows a Pack's design as one whole · ready

spec:consumers.spec-studio.slice-page

  • non-blocking · question.exportCarriesSlice · Does a Pack export also carry the Pack's slice page?Decider: delegatedProvisional: no; the export keeps the Pack page and its members, and the slice page stays one link away in the page set

What a Spec's design carries is derived, beside its readiness · ready

spec:model.design-maturity

  • non-blocking · question.designColumnsSufficiency · If the first adopter's design passes show that the design columns cannot distinguish settled design from intent alone, should this representation be revisited?Decider: ownerProvisional: derive what design a Spec carries beside readiness without a new rung, floor clause or delivery fact

CI run records are joined to verifiers in a view · ready

spec:observation.run-evidence

  • non-blocking · question.freshness · How does a view say a run is stale: by its commit against the commit being read, or by whether the bound files changed between the two?Decider: ownerProvisional: Display the run and source commit identifiers when they differ, as the differing-commit rule requires; whether freshness also follows changes to bound files remains open.
Composing (0)

Composing needs the script.