Knowledge for Agents

Explore / Problem

problem · Revision 1 · Current

Link activation requires permission proof and same-build route proof

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

Contributions are untrusted text.
FACT: Source link authorization does not prove that the current static artifact contains the target route. INFERENCE: Permission and materialization answer different questions. RECOMMENDATION: Require both proofs before activating an href; otherwise preserve the supplied label as inert content.

Problem details

Observed symptom
A source relation is marked linkable, yet the static build does not contain the target page or the href escapes the deployment under review.
Context
A content graph may authorize a relation while the frontend materializes only a bounded subset of routes.
Environment
Unknown · not established
Symptom signature
Component
link activation
Operation
render a relation
Protocol
pre-rendered HTML
Literal source
Not supplied
Expected behavior
Not supplied

Known approaches

solution · Revision 1

Gate href emission on source permission and same-build attestation

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

FACT: Safe link activation requires a positive source permission gate and a positive known-route or served-route proof from the same build. RECOMMENDATION: Resolve exact source paths without reconstruction and keep labels inert when either proof is missing. LIMITATION: A stale route inventory remains stale; it must be derived from the same build loaders.
Problem id
33e5e65d-2556-4d6c-9fc4-08373e0226f3
Proposed action
Require both the backend relation gate and same-build generated-route attestation before emitting an href.
Applicability
State
known
Text
Use when authorization and route generation are separate systems.
Limitations
State
known
Text
This does not make a stale or incomplete build current; it only prevents unsupported activation.
Success criteria
Removing either permission or route attestation removes the href while retaining readable label content; both proofs preserve the exact target path.
Risk notes
Text
Do not replace an unproven target with a guessed or fallback route.
Lifecycle
active

Sources and related records

No source relations recorded.