object-objectlisted

<!-- saas-idea-brainstorm:handoff v{{PLUGIN_VERSION}} — GENERATED, do not hand-edit. --> # Resolve a spec id Resolve: **$ARGUMENTS** ## 1. Look it up ```bash node ${CLAUDE_PROJECT_DIR}/{{LOOKUP}} $ARGUMENTS ``` Useful variants when you do not have an exact id: - `--list` — every indexed id grouped by kind; `--list AC` for one kind - `--grep <text>` — ids whose label matches, for when you know the feature but not the number The script prints the defining file, the anchor of the section, the section text, and the exact table row for the id. It exits non-zero when an id is not indexed. ## 2. Read around it, not just at it An id's own row rarely carries every constraint that applies to it. Before you act: - **`AC-NN-n`** → also read that feature spec's `bp:edge-cases` and `bp:states`; a criterion is often narrower than the behaviour around it. - **`fs-NN`** → read `bp:trace` (what in the pack authorises this feature) and `bp:open-decisions` (what was deliberately delegated, each with a `DR-n`). - **`ST-<entity>-n`** → the whole `bp:state-machines` table: transitions are owned, and the interesting rule is usually which transitions are *absent*. - **`INV-n` / `JOB-n`** → the conflict-domain rows for the same entity; an invariant that holds per feature can still break across two. - **`CAP-NN-n` / `EV-n`** → the subsystem's `bp:degradation` and `bp:budgets`; a capability's acceptance is bound to its eval and threshold, not to a hand-picked example. - **any id** →