Everything you need
to run it well.
Docs, guides and field notes — from your first locked baseline to tuning the autonomy ladder. Written to be read on a laptop in a site office.
Docs by area.
Getting started
Create a project, plan the WBS, lock a baseline, and get your first autopilot verdict.
Guide →The engine explained
P, I, D, the human factors and how a verdict decomposes. Read the arithmetic behind the number.
Reference →The field app
Rolling out offline daily updates, crew logs and evidence capture in हिंदी / मराठी.
Guide →Admin & governance
Workflows, approval gates, change control, the audit trail and the autonomy ladder.
Guide →HQL search
The query language — fields, operators, saved filters and did-you-mean.
Reference →API & webhooks
Integrate with Slack, Teams and your systems of record. Events, payloads and auth.
Reference →Practical playbooks.
How to read a verdict
What NEEDS ATTENTION means, and the first three things a PMO lead should do with it.
Setting the autonomy level
Choosing A0–A2 for your organisation, and when to keep the kill switch close.
Onboarding a subcontractor
Bringing an EPC party in as a governed actor with SLAs and acceptance.
Migrating from Jira
The 10k-issue import — JSON or CSV, zero silent drops, idempotent re-runs.
From the blog.
Why your Gantt is a lagging indicator
Schedules record what already happened. Here's what it takes to measure drift while you can still act on it.
The 45-second update, and why it matters
If the crew leader won't log it, the engine is blind. Designing for one bar of signal.
Explainable by default
Why every recommendation ships its arithmetic — and what that costs us to guarantee.
More coming as we go — subscribe from the contact page.
Can't find what you need?
Ask us directly — we'll point you to the right doc, or write the one that's missing.