Problem
What customer problem did the system address?
PROOF, NOT CERTIFICATION
Publish the work.
Show what remains true when it fails.
A Field Report turns a project into inspectable evidence: problem, constraints, architecture, failures, measurements, tradeoffs, and limitations.
COPYABLE STRUCTURE
Operating context
Who uses it, where does it run, and what matters if it fails?
Constraints
Latency, cost, security, compliance, reliability, integration, and time.
Architecture
Show the system diagram, authority boundaries, and data flow.
Implementation
What did you build, and deliberately not build?
Failure model
What can fail across model, context, tools, data, infrastructure, and people?
Failure tests
What did you break intentionally, and what invariant did you expect?
Evaluation
How did you measure behavior and customer-facing quality?
Results
Show raw evidence, comparisons, and operating conditions.
Tradeoffs
What did the architecture gain and give up?
Known limitations
What remains unsafe, fragile, expensive, or unproven?
Evidence
Link repo, tests, evals, traces, screenshots, benchmarks, and deployment.
Next decision
What changes before this serves a real customer?
SELF-REVIEW RUBRIC
Grade the evidence, not your effort.
Not demonstratedDemonstratedStrongly demonstrated
- 01Problem clarity
- 02Architecture
- 03Failure reasoning
- 04Evaluation
- 05Evidence
- 06Reproducibility
- 07Security
- 08Operations
- 09Tradeoffs
- 10Communication