Source: https://guthlabs.ai/docs/jobs/stan-architecture-and-implementation/tools/

job / candidate

# Architecture and implementation — tools

The distinct tools record for Architecture and implementation. This page is proposal-only.

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

## Record status

**Record ID**: job:stan:architecture-and-implementation

**Parent lifecycle**: candidate

**Page lane**: package

**Lane lifecycle**: proposed

**Owner**: Stan

**Owner role**: Chief Security and Engineering Officer

**Owner status**: VERIFIED

**Qualification result**: NOT RUN · held for evidence and human review

**Working browser surface:** [Agent jobs — builder overview](<https://guthlabs.ai/guth.html#builder>) — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Authoritative package lane tools and interfaces

### Canonical tools-page assignments

- **Assurance preflight** (skill · required) — Use for structured security and architecture preflight before proposing sensitive changes.

- **Terminal courier** (interface · required) — Use only for bounded local staging or relay of implementation material; it does not authorize deployment or external effects.

- **Receipt ledger** (record · required) — Preserve proposals, evidence, decisions, holds, and review receipts.

- **Source-bound recall** (skill · required) — Keep architecture and implementation claims tied to source records, locators, revisions, and provenance.

- **Security field guides** (guide · required) — Provide bounded procedures for security review and failure handling.

- **Supabase field guide** (guide · optional) — Use only when the source-bound request concerns Supabase; provider and database effects remain held.

- **Cloudflare operations** (guide · optional) — Use only for source-bound Cloudflare operations planning; deployment and provider effects remain held.

- **Current-work packets** (guide · required) — Maintain continuity, ownership, dependencies, and open loops across bounded engineering work.

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

### Canonical tools-page assignments

No verified instrument is assigned to this tools lane.

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

## Use boundary

- Treating Stan's verified owner status as permission to execute gated effects.

- Manufacturing Antonio's authority or assigning decisions to an unverified principal.

- Converting a proposal, local prototype, or staged command into deployment or provider activity.

- Assuming credentials, databases, customers, publication, or production infrastructure exist or are connected.

- Using confidence, memory, or an unverified source in place of source-bound evidence.

- Destroying or altering records during remediation without a reversible plan and human approval.

- Losing continuity through missing owners, deadlines, revisions, receipts, or unresolved-loop notes.

- Exposing credentials, protected data, incident details, or sensitive architecture in ordinary notes or messages.

- Presenting educational or preliminary calculations as engineering approval or safety certification.

- Accessibility failures that hide held, failed, or needs-review states from keyboard or assistive-technology users.

## Sources and evidence

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

- `agents/index.html#stan`

- `source_record:job:stan:architecture-and-implementation`

- `source_record.owner_status=VERIFIED`

- `source_record.existing_tools`

- `source_record.existing_guides`

- `source_record.principal_gates`

- `source_record.never_rules`

- `OBSERVED_NATIVE_CONTRACT`

- `APP_ROUTES`