A Pack is read from a named perspective

actor

A reviewer or an agent who reads a Pack for one concern, such as the domain model, operations or the runtime platform.

problem

Every reading of a Pack shows every member in the same order with the same emphasis, so a reader with one concern sorts it by hand, and an adopter keeps its perspectives as prose briefs the graph cannot apply.

outcome

Let a reviewer read the same Pack from one perspective at a time, filtered and ordered for that perspective, without a new kind or a stage.

rule.contentIntact line 22 · specs/consumers/review-perspectives.sdp.md:22

A perspective filters and orders a Pack's members and leaves each selected member's content intact; every row opens the same Spec, and the whole Pack stays one step away.

no example exercises it

rule line 23 · specs/consumers/review-perspectives.sdp.md:23

A perspective adds no kind, readiness, stage or sequence; reading a Pack from one perspective records nothing, and no perspective is required before another or before ready is stated.

rule line 24 · specs/consumers/review-perspectives.sdp.md:24

The corpus owns its perspectives and their questions; the Protocol supplies the filter and ships no list of perspectives.

rule line 25 · specs/consumers/review-perspectives.sdp.md:25

A perspective is corpus data: a JSON object the corpus keeps beside its briefs and passes to the perspective filter, a catalog recipe, through --params. The reader loads no perspective file, and no validator lists or checks perspectives, so no registry forms.

rule line 26 · specs/consumers/review-perspectives.sdp.md:26

A perspective selects members by Spec id or id prefix, kind, section presence, Design key with an optional value, question key, and authored relation type with a stated direction; it selects component layer or context only through the member's code unit bindings, satisfying or referencing, that the perspective names; it infers nothing from prose, paths or imports.

rule line 27 · specs/consumers/review-perspectives.sdp.md:27

A member selected by a Design key, including the layer and context keys a component design states, is selected on declared intent; a member selected through a binding's component is selected on anchored structure; each row names which, and the two are never merged into one architecture answer.

rule line 28 · specs/consumers/review-perspectives.sdp.md:28

Values within one selector are alternatives and different selectors combine as requirements; an unsupported selector is a diagnostic in the result, and a valid selector that matches nothing is an explicit empty result.

rule line 29 · specs/consumers/review-perspectives.sdp.md:29

Members keep the manifest's authored order unless the perspective gives an explicit priority order, authored order breaking ties; every selected member's blocking questions stay visible whatever else the perspective filters out.

7 unkeyed rules.

perspectiveObject line 33 · specs/consumers/review-perspectives.sdp.md:33

{ "name": "models", "select": { "kinds": ["model"] } } selects the members of kind model. A perspective is { name, select, order } with select and order optional, and its selectors are ids, idPrefixes, kinds, sections, designKeys, questionKeys, relations and bindings, each optional; different selectors combine as requirements. An absent selector imposes no requirement, a present empty list matches no member, and an absent or empty select object selects every member. A designKeys item is { key, value } with value optional; a relations item is { type, direction, target } with direction out or in and target optional; bindings is { via, layers, contexts }, where via is required and lists satisfies or references, and absent layers or contexts impose no restriction. order lists Spec ids by priority, authored order breaking ties.

no citation recorded

perspectiveRecipe line 34 · specs/consumers/review-perspectives.sdp.md:34

recipe 37, the perspective filter, takes params.pack and params.perspective and returns { pack, perspective, totals: { members, selected }, diagnostics, selected, notSelected }.

perspectiveRows line 35 · specs/consumers/review-perspectives.sdp.md:35

each selected row is { id, matchedOn: [{ selector, value, claim }], blockingQuestions: [{ address, question }] } in the perspective's order and then authored order; claim is declared for a match on authored intent and anchored for a match through a binding; notSelected lists the remaining member ids in authored order.

perspectiveDiagnostics line 36 · specs/consumers/review-perspectives.sdp.md:36

an unknown selector, a value of the wrong type or a bindings selector with no via is a diagnostic row { selector, problem }, and the recipe still applies the selectors it understood.

Verifier bindings

• test:protocol.perspective-filter-recipe · anchored · test anchor binding present · test/iteration-recipes.test.ts:760

  External run evidence from test/iteration-recipes.test.ts

  Test anchors: test:protocol.context-bundle-recipe, test:protocol.design-diff-recipe, test:protocol.perspective-filter-recipe, test:protocol.proposal-schema-and-recipe. Specs verified by those bindings: spec:consumers.context-bundle, spec:consumers.design-diff, spec:consumers.intent-composition.proposal, spec:consumers.review-perspectives.

  Run 1: external run evidence from vitest 4.1.10

  Build: CI 380 · Branch: feature/roadmap-and-slices-v0 · Commit: 34909918bf0be0e849959644401797191cae379f · Start: 2026-10-22T17:40:31.456Z · Stop: 2026-10-22T17:42:16.171Z

  Name	Suite	Result	Duration
  compares keyed values, keyed order and unkeyed sections while keeping bindings apart	iteration loop: design diff	passed	72.53 ms
  compares question fields by key, whole unkeyed questions, envelope fields and other sections	iteration loop: design diff	passed	30.62 ms
  reports added and removed Specs and Packs, filters the union of membership, and ignores source lines	iteration loop: design diff	passed	40.64 ms
  diagnoses required input and schema differences and compares common content	iteration loop: design diff	passed	12.84 ms
  runs the documented base-worktree procedure, preserves constant anchors, and compares HEAD	iteration loop: design diff	passed	24191.88 ms
  compares a keyed rule that becomes a flow at the same address	iteration loop: design diff	passed	40.12 ms
  compares new Design entries across schema versions when the base corpus has none	iteration loop: design diff	passed	20.7 ms
  diagnoses uncertain optional fields at base 0.9.0 and head 0.9.0	iteration loop: design diff	passed	12.31 ms
  diagnoses uncertain optional fields at base 0.9.0 and head 0.10.0	iteration loop: design diff	passed	14.37 ms
  diagnoses uncertain optional fields at base 0.10.0 and head 0.9.0	iteration loop: design diff	passed	25.38 ms
  normalizes legacy rule markers in graphs with comparable rule-key capability	iteration loop: design diff	passed	14.26 ms
  invents no order across rules and flows from a legacy base	iteration loop: design diff	passed	24.92 ms
  compares a legacy base's keyed entries by order within each list	iteration loop: design diff	passed	28.06 ms
  reports proposal scopes outside the common schema as incomparable	iteration loop: design diff	passed	13.58 ms
  lists all authored reasons into and out of the planning subject in type/from/to order	relation reasons in planning recipes	passed	19.97 ms
  keeps dependency reasons in context-bundle footing	relation reasons in planning recipes	passed	9.01 ms
  matches every declared selector, combines requirements, and keeps authored order unless prioritized	iteration loop: perspective filter	passed	55.16 ms
  matches layers and contexts only through named bindings and keeps anchored matches apart	iteration loop: perspective filter	passed	32.84 ms
  reports malformed and unsupported selectors while applying understood ones	iteration loop: perspective filter	passed	33.17 ms
  keeps term addresses, term lines and key maps through the section cut	iteration loop: context bundle	passed	26.54 ms
  keeps questions and declarations in one place and member-example steps only in their member row	iteration loop: context bundle	passed	19.18 ms
  takes the declaration cut last only with addresses and keeps compact pointers and links	iteration loop: context bundle	passed	77.64 ms
  cuts a pinned dotted key to its line when it has no entry address	iteration loop: context bundle	passed	46.93 ms
  composes both scopes, dependency footing, declarations, example bindings and a perspective subset	iteration loop: context bundle	passed	24.38 ms
  takes all six whole-mode cuts in fixed order and counts the complete returned value including Unicode	iteration loop: context bundle	passed	45.42 ms
  keeps a pinned declaration whole through the sixth cut when its key contains a dot	iteration loop: context bundle	passed	18.09 ms
  reports invalid, missing, doubled and unknown scopes without a partial bundle	iteration loop: context bundle	passed	39.62 ms
  accepts term scopes and detects changed definitions through their authored keys	iteration loop: proposal schema and check	passed	27.58 ms
  holds the schema and recipe to the same accepted and refused documents	iteration loop: proposal schema and check	passed	115.66 ms
  checks the complete scope union, resolves both graphs, and reports each change independently	iteration loop: proposal schema and check	passed	18.38 ms
  agrees with recipe 35 on added, removed and changed entry values and on whole-Spec changes	iteration loop: proposal schema and check	passed	28.57 ms
  excludes anchor-only changes and requires the caller's base graph	iteration loop: proposal schema and check	passed	29.83 ms
  compares interleaved keyed rules and flows in their authored order and reports verifier changes apart	iteration loop: comparison and budget edges	passed	31.26 ms
  cuts example text once and preserves compact pointers after the sixth cut	iteration loop: comparison and budget edges	passed	32.28 ms
  reads the base graph and proposal from named JSON files through the real parameter seam	iteration loop: comparison and budget edges	passed	9.74 ms
  requires a test bound directly to an example before the bundle names it enabled	iteration loop: example enablement	passed	15.3 ms
  compares rule order by text and other anonymous collections as a whole	iteration loop: anonymous collection order	passed	25.17 ms
  keeps addresses in each place when narrative, example, question and section text are cut	iteration loop: protected entry addresses	passed	56.27 ms

Requirement drawing

• Declared verifying examples: no declared verifying example.

Decisions

No decision record named.

• impl:protocol.perspective-filter-recipe · realizes the perspective filter in the shipped recipe catalog · test/iteration-recipes.test.ts:753

  Uses

  None.

Runtime observation: not tracked.

Runtime observation: not tracked.

Build attestations: not tracked.

Deployments: not tracked.

Bills of materials: not tracked.