Sample Generated Asset

From ledger to onboarding doc — automatically.

This is an actual ADAMAS output format: an onboarding document generated from the sample decision ledger. Every section is traced back to the ledger entries it was built from — that's the SRC tag you'll see throughout.

Sample data — illustrative
onboarding_automation-engineer.md generated by ADAMAS from ledger v2025-05 · 14 decisions · sample

Onboarding: Automation Engineer

For new engineering hires · Generated from the company decision ledger · Replaces 3–4 months of shadowing with a structured first month

Why this document exists SRC: HIR-009, OPS-013

Until 2024, new engineers learned by shadowing the two most senior people — who were also the bottleneck on every project. After a senior departure took nine years of undocumented context with it, the company decided that onboarding would be generated from the decision ledger and kept current quarterly. You are reading the result.

How we quote work SRC: SAL-011, FIN-022, SAL-017

No fixed price without paid discovery. Two projects overran 40%+ when scope was quoted from a single meeting; since June 2024 every fixed-price quote requires a 2–5 day paid discovery phase. Quotes after discovery have landed within 10% of actuals.

  • Every fixed-price quote carries a visible 15% contingency line; 5% is rebated at acceptance if unused. Clients see the honesty, we keep the buffer.
  • Rate card: new-client rates were raised 12% in January 2025; existing clients are grandfathered for 12 months. Check which card applies before you estimate.

How we deliver on site SRC: OPS-020

No solo commissioning, ever. A solo visit in early 2025 nearly caused a safety incident on an undocumented machine state. Every site visit is two people minimum — one may be junior, and as the new hire that will often be you. This is priced into every quote; never offer to waive it to win a deal.

The platform you'll work in SRC: PRD-019, PRD-008

Siemens TIA Portal is the default for all new projects (standardized February 2025 — context switching across three ecosystems was killing library reuse). Other platforms only when the client's installed base demands it, priced accordingly. Legacy SCADA maintenance is sunset: existing contracts run to expiry, no new ones.

Who decides what SRC: OPS-005, HIR-018

  • Project decisions — your PM (promoted internally January 2025; she coordinated the three largest builds before that).
  • Pricing exceptions, client acceptance, anything touching the rate card — founder, at the Friday decision review.
  • Anything not covered here — bring it to Friday's 30-minute decision review. That's where this ledger grows; one day your decisions will onboard your successor.

Your first 30 days

  1. Read the 25-decision reading path in the ledger (your lead assigns it — about 90 minutes total).
  2. Pair on one active commissioning project as the second person (see two-person rule above).
  3. Log your first decision at a Friday review — even a small one. Writing the why is the habit that makes everything above stay true.

This document was assembled from 9 of the 14 entries in the sample ledger — nothing in it was written separately. When a decision changes, the document regenerates. Explore the ledger it came from →

Book a Clarity Audit →