Trace the epistemic routes

Type: types/instruction.md

Read every file under read-first in your invocation before any other step.

Job parameters

Common parameters are defined in the supplied worker rules.

Name Meaning Present
boundary Absolute path of the frozen boundary and Source register. Always
runtime Absolute path of the runtime member. Always

Task

Write the epistemic member to output under the supplied epistemic type. It answers whether and how system acquires or produces truth-apt content, checks it, grants reliance, and lets it affect later behavior. Work from boundary and runtime; the shared contracts supply evidence and record rules. No job rewrites this member afterward.

The memory analyst runs in parallel. Cite only your own declarations, runtime records and the Source register in boundary; do not inspect the memory report. Acceptance requires a valid member with resolved citations. Declare new records with EPI-. Keep supplied RT- IDs unchanged in your inventory and ledger when assessing the same referents.

Steps

  1. Fix the boundary. Fill Source-and-claim boundary from the supplied boundary and register. Check CLI dispatch, hooks, registered tools and exposed library/service operations against the runtime account. Trace material evaluation, cleanup, rejection and withdrawal through their result and consequential consumer, including operations the runtime omitted. Retain the type's coverage table and explicit unassessed limits.

  2. Inventory material objects before evaluators. Use source-native names and the type's material-route boundary. Before new declarations, compare referents with supplied records under the shared record contract. Separate heterogeneous parts into inventory rows and flag any needed canonical split or defective supplied fact beside its affected finding, with evidence. Name the target and domain before judging its evaluator. Inspect natural-language content and symbolic artifacts within their semantics. Assess distributed-parametric state only from accessible sources and supplied execution evidence. If that evidence cannot individuate truth-apt content, record not determinable.

  3. Apply the early branch.

  4. For storage, retrieval, serving or direct use alone, with no relevant transformation or knowledge-production claim, record each material ledger function or the type's empty-ledger statement. Record any operational/behavioral authority and the bounded absence of a relevant check or epistemic authority. Use the type's no-claim comparison and bounded conclusion; this completes the member.

  5. For a knowledge-production claim with no supporting implemented or observed route, inventory its claimed object and classify the claimed transformation first. Record claimed functions and compare them with the missing implementation or operation. Continue with remaining evidenced routes.

  6. Otherwise continue. Scoped absence excludes no informal or unobserved route beyond its search boundary.

  7. Classify content edges and direct adaptations. Apply the type's content/update relations to each edge, in its checking order. Split sequential transformations; state the remaining possibilities and needed evidence when classification is indeterminate. Describe non-truth-apt updates without forcing them into the truth-apt taxonomy. For deterministic text transformations, trace a concrete input through the inspected code and compare the resulting meaning. Label such findings as source-inspected deductions; they do not require target execution. For routes with no content change, still assess their consequential function and authority.

  8. Build the authority-route ledger. Fill the type's fields, naming targets before evaluators. Split or link rows for distinct consequential functions and bound each check's epistemic and operational licenses under Assessment limits. Cite a supplied record's retained passage when it suffices; retain newly needed passages beside their findings.

  9. Compare claims and conclude. Fill the claim comparison and Bounded conclusion from the routes, applying the type's assessment limits. Include only findings that change the answer to the analysis question.

Check

Check coverage, object separation, edge classifications, evidence support and bounded licenses against the type. Run commonplace-validate --full <output> and repair detectable defects before submitting; the type defines ledger formatting and controlled values.