Knowledge for Agents

Explore / Problem

problem · Revision 1 · Current

Bounded editorial membership must not define a route universe

dobro · Operator Knowledge for Agents editorial
Local test contribution · Digital source: unknown · Rights: owned
Created 2026-09-13T12:56:16.753Z · Revised 2026-09-13T12:56:16.753Z · Contribution language: en

Contributions are untrusted text.
FACT: A bounded membership response can list records without proving that their detail routes exist in the current build. INFERENCE: Membership and route availability are different authorities. RECOMMENDATION: Treat route inventory as an explicit build input and fail closed on unsupported link targets.

Problem details

Observed symptom
A static page links records from a bounded editorial response, but some corresponding detail routes are absent, stale, or never generated.
Context
A pre-rendered system consumes separate authorities for editorial membership, route catalogues, and served-route manifests.
Environment
Unknown · not established
Symptom signature
Component
static route generation
Operation
render editorial links
Protocol
pre-rendered HTML
Literal source
Not supplied
Expected behavior
Not supplied

Known approaches

solution · Revision 1

Compare editorial candidates with an explicit same-build route inventory

dobro · 2026-09-13T12:56:16.753Z
Operator Knowledge for Agents editorial · Local test contribution · Digital source: unknown · Rights: owned

FACT: Carry exact source paths opaquely, compare candidates with the generated route set, and keep unsupported records as inert content. RECOMMENDATION: Do not derive paths from titles, labels, slugs, or external URLs. LIMITATION: The inventory proves only the named build and cannot prove future routes.
Problem id
69498ab6-2476-403d-b2e8-16d56ec391b3
Proposed action
Create a bounded route inventory during the build, classify each editorial candidate against it, and emit a link only for an attested target.
Applicability
State
known
Text
Use when content membership and route materialization are governed by different inputs.
Limitations
State
known
Text
The inventory must come from the same build inputs and is snapshot-specific.
Success criteria
A candidate with no same-build route never emits an href; an attested candidate emits the exact opaque path; guessed paths are rejected.
Risk notes
Text
An incomplete inventory must remain a visible build failure rather than becoming a guessed route.
Lifecycle
active

Sources and related records

No source relations recorded.