grok14ENGINEERING FIELD SCHOOL
Field resources

The delivery toolkit.

Reusable working documents for discovery, architecture, evaluation, releases, incidents, and portfolio evidence.

Reusable field template

Client discovery brief

Problem and workflow · Accountable owner and users · Evidence versus stakeholder claims.

Download Markdown template
Preview the sections
  1. Problem and workflow
  2. Accountable owner and users
  3. Evidence versus stakeholder claims
  4. Baseline or measurement plan
  5. Pilot scope and action boundaries
  6. Authoritative data and access
  7. Integration dependencies
  8. Acceptance criteria and review method
  9. Risks, owners, and decisions
  10. Milestones and handoff
Reusable field template

Architecture decision record

Decision ID, date, status, owner · Context and constraints · Alternatives, including a simpler baseline.

Download Markdown template
Preview the sections
  1. Decision ID, date, status, owner
  2. Context and constraints
  3. Alternatives, including a simpler baseline
  4. Selected option and rationale
  5. Evidence: dataset, versions, results
  6. Quality, safety, latency, and cost tradeoffs
  7. Identity, access, and operational implications
  8. Assumptions and residual risks
  9. Reconsideration triggers
  10. Links to tests and implementation
Reusable field template

Evaluation report

Task and success definition · Dataset version, provenance, and split · Case categories and denominators.

Download Markdown template
Preview the sections
  1. Task and success definition
  2. Dataset version, provenance, and split
  3. Case categories and denominators
  4. Application, prompt, model, and retrieval versions
  5. Scorers and human-review calibration
  6. Baseline and candidate results
  7. Critical access and approval checks
  8. Latency, load, and cost conditions
  9. Failure examples and limitations
  10. Release recommendation and owners
Reusable field template

Release and rollback checklist

Artifact and source revision · Dependency and configuration versions · Target environment and service identity.

Download Markdown template
Preview the sections
  1. Artifact and source revision
  2. Dependency and configuration versions
  3. Target environment and service identity
  4. Code, contract, integration, and evaluation results
  5. Permissions and negative tests
  6. Migration compatibility
  7. Smoke tests and expected outputs
  8. Rollout cohort and stop criteria
  9. Rollback steps and non-reversible effects
  10. Monitoring owner and resource cleanup
Reusable field template

Incident runbook

Service, environment, owner, escalation contact · Symptoms and user impact · Safe diagnostic commands and dashboards.

Download Markdown template
Preview the sections
  1. Service, environment, owner, escalation contact
  2. Symptoms and user impact
  3. Safe diagnostic commands and dashboards
  4. Containment: disable writes or affected path
  5. Evidence and timeline preservation
  6. Dependency, data, identity, and recent-change checks
  7. Recovery or rollback procedure
  8. Validation before declaring recovery
  9. Stakeholder update template
  10. Postmortem actions, owners, and due dates
Reusable field template

Portfolio case study

Project type: coursework, simulation, or employment · Problem, client context, and your actual role · Constraints and assumptions.

Download Markdown template
Preview the sections
  1. Project type: coursework, simulation, or employment
  2. Problem, client context, and your actual role
  3. Constraints and assumptions
  4. Architecture and alternatives
  5. Implementation and tested environment
  6. Results with evidence and sample limitations
  7. Failures and decisions they changed
  8. Security, operation, and handoff
  9. Demo and artifact links
  10. Next validation or improvement

Write for the decision

Use these templates as working documents, not paperwork to fill mechanically. Keep the main point visible, attach evidence, and make assumptions and decisions easy to find. A two-page brief that resolves ambiguity is more valuable than a long document that hides it.

Templates intentionally contain writing fields. They are learner worksheets, not unfinished course pages.