Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

field guide / candidate

Current-work packets — tools

The distinct tools record for Current-work packets. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
field-guide:current-work-packets
Parent lifecycle
candidate
Page lane
tools
Lane lifecycle
proposed
Owner
Stan
Owner role
Not separately recorded
Owner status
Not separately recorded
Qualification result
NOT RUN · held for evidence and human review

Working browser surface: Field guides — documentation — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Authoritative tools lane tools and interfaces

Canonical tools-page assignments

  • Notebook Field Guides (interface · required) — Use /app/notebook/field-guides/ to present this bounded procedure, prerequisites, steps, and related instruments; do not infer that the guide is published externally.
  • Notebook Notes (interface · required) — Use /app/notebook/notes/ for source-labelled current-state notes, observations, unknowns, and revision-aware claims.
  • Notebook Files (interface · required) — Use /app/notebook/files/ for local file references and provenance beside the packet; do not describe this as upload or protected storage.
  • Notebook To-dos (interface · required) — Use /app/notebook/to-dos/ for owned milestones, due dates, priorities, completion state, tags, and human-review signals.
  • Notebook Approvals (interface · required) — Use /app/notebook/approvals/ for decisions and consequential proposed actions, with Needs review, Approved, or Held status.
  • Notebook Agent Logs (interface · required) — Use /app/notebook/agent-logs/ to preserve authority boundaries, current state, receipts, and the final handoff revision.
  • PointGuard (interface · required) — Use /app/pointguard/ as the contextual room for the current packet and linked Notebook work; it is a cross-app context surface, not the canonical owner of specialist execution records.
  • Current-work packet template (guide · required) — Use this field guide as the repeatable structure for identity, evidence, workback, risks, authority limits, and receipt-backed handoff.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

  • Confusing a local prototype or index with a connected provider, database, customer system, or production workflow.
  • Treating a native route name as evidence of deployment or external capability.
  • Attaching unverified evidence or losing source locators and revisions.
  • Assigning shared or ambiguous ownership, causing silent handoff failure.
  • Using countdown or date calculations as automatic reminders or authoritative scheduling.
  • Marking work complete when approval, evidence review, or recipient acknowledgement is still missing.
  • Publishing unsupported operational, security, customer, or qualification claims.
  • Creating inaccessible status or validation cues that rely on color, hover, or pointer-only interaction.

Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

  • source_record:field-guide:current-work-packets
  • agents/index.html#stan
  • Observed native contract: Notebook collections, deadlines, records, PointGuard, and held web boundary
  • App route: /app/pointguard/
  • App route: /app/notebook/notes/
  • App route: /app/notebook/files/
  • App route: /app/notebook/to-dos/
  • App route: /app/notebook/approvals/
  • App route: /app/notebook/field-guides/
  • App route: /app/notebook/agent-logs/
  • App route: /app/notebook/projects/