Source: https://guthlabs.ai/docs/field-guides/security-field-guides/forms/

field guide / candidate

# Security field guides — forms

The distinct forms record for Security field guides. This page is proposal-only.

Status: **proposed**Lifecycle: **candidate**

## Record status

**Record ID**: field-guide:security-field-guides

**Parent lifecycle**: candidate

**Page lane**: plan

**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](<https://guthlabs.ai/docs/field-guides/>) — Inspect the guide and persist local checkpoints. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Proposed form sections

Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth.

### Guide identity and ownership

Capture the canonical identity and explicit ownership without expanding the supplied scope.

- title

- slug

- record type

- lane

- owner agent

- related jobs

- lifecycle

- visibility

### Source boundary

Preserve the supplied source locator and distinguish observed facts from proposed content.

- source record ID

- source references

- source locator

- source SHA-256 if available

- provenance note

- observed facts

- proposal-only boundary

### Procedure definition

Describe the intended guide workflow and its checkpoints without asserting an implemented security capability.

- purpose

- prerequisites

- ordered steps

- checkpoint criteria

- failure branches

- evidence required

- record owner

### Deadlines and handoffs

Make unresolved work visible through explicit human-owned deadlines.

- work item

- owner

- priority

- due date

- dependency

- recurrence candidate

- completion state

- handoff receipt

### Review and completion

Record review disposition and deterministic completion status.

- reviewer

- review decision

- approval receipt

- open risks

- acceptance tests

- completion criteria

- held claims

### Accessible state contract

- Every field requires a visible and programmatic label.

- Required and optional fields must be stated in text.

- Invalid entries require an actionable message linked to the field.

- Blocked and Held states remain visible without relying on color alone.

## Supporting documentation fields

These fields come from the tools lane and remain separate from the primary operating form.

### Scope and ownership

Define the bounded security task, accountable owner, and evidence boundary.

- guide title

- security task type

- owner agent

- human reviewer

- related job

- related project

- source record ID

- source locator

- scope statement

- out-of-scope effects

### Inputs and evidence

Capture only supplied or locally reviewed inputs with provenance.

- input description

- record ID or file reference

- source locator

- source SHA-256 if available

- capture date

- revision

- visibility

- sensitivity classification

- missing-input note

### Workback and deadlines

Make review timing explicit and preserve held external effects.

- start date

- review deadline

- handoff deadline

- priority

- recurrence candidate

- dependency list

- escalation threshold

- completion state

### Bounded procedure

Record ordered checks, tool use, expected outputs, and stop conditions.

- step ID

- action

- designated tool

- input fields

- expected result

- failure state

- stop or escalate condition

- receipt reference

### Review and handoff

Require human review before consequential communication or external effect.

- review status

- reviewer

- review timestamp

- findings

- residual risk

- approved local action

- held external action

- handoff recipient

- handoff receipt

## Required or proposed record references

No record existence is asserted by this documentation page.

- field-guide:security-field-guides:plan

- source record field-guide:security-field-guides

- owner agent Stan record or agent reference

- one source-labelled note containing the scope decision

- one receipt-backed approval record before any lifecycle change

- linked to-do records for unresolved prerequisites and deadlines

- source-labelled security note

- field-guide record

- linked job or project record

- validation receipt

- review or approval record

- follow-up to-do

- incident or handoff log

## Sources and evidence

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

- `source_record:field-guide:security-field-guides`

- `agents/index.html#stan`

- `field-guide:security-field-guides`

- `Observed native contract: project_and_field_guide_collections`

- `Observed native contract: deadlines`

- `Observed native contract: records`

- `Observed native contract: pointguard`