Architecture and implementation — field guides

Record status

Record ID

job:stan:architecture-and-implementation

Parent lifecycle

candidate

Page lane

docs_urls

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 — Inspect the package and stage a local project. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

Related field-guide records

• /app/notebook/field-guides/

Source-proposed guide paths are references, not proof that those paths resolve.

Operating sequence

1. Create or locate the canonical job record and preserve its source locator, provenance, revision, and lifecycle.
2. Open a current-work packet identifying the request, owner, reviewer, context, and unresolved loops.
3. Classify the request as preparation, review, remediation, incident command, continuity work, or an effect requiring a principal gate.
4. Collect only source-bound inputs; label assumptions, missing evidence, and sensitive material explicitly.
5. Review architecture and security boundaries, including ownership, data custody, access paths, failure states, and continuity requirements.
6. Break implementation into reversible, bounded tasks with explicit dependencies, deadlines, workbacks, and human review points.
7. Use Assurance preflight before proposing security-sensitive changes or remediation.
8. Use Source-bound recall to verify claims against linked records rather than confidence or memory.
9. Use Terminal courier only to stage or relay bounded local implementation material; do not treat it as deployment authority.
10. Record proposed outputs and evidence in the Receipt ledger, including unresolved failures and held effects.
11. Route destructive remediation, money or purchasing, credential changes, public deployment, and legal filing to the appropriate human approval state.
12. Preserve the final packet, decisions, revisions, and continuity notes in Notebook surfaces for later review.

Handoff 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
• source_record.owner_agent=Stan
• source_record.owner_role=Chief Security and Engineering Officer
• observed_native_contract.records
• observed_native_contract.pointguard
• app_routes=/app/pointguard/
• app_routes=/app/notebook/agent-logs/
• app_routes=/app/notebook/approvals/
• app_routes=/app/notebook/projects/
• app_routes=/app/notebook/search/