autotelic.build(720) 287-7958

Sheet G-000 · Cover sheet

How Autotelic works: an AI-run design-build system

Eight modules run every project. Open a module, or pick a configuration to follow it from feasibility to the field.

Start at Feasibility

Every space is built for a purpose, and every purpose is a person — the guest a room is for, the owner who has it built. Designed for appeal. Engineered to function. Autotelic builds the room and brings the guest.

GUESTPLATFORMOWNERBRINGBUILDSITEBUILDINGROOMOWNER → HOST
SheetTitleShows
G-000Cover sheetThe statement, the form, the sheet index.
A-100Platform assemblyThe eight modules exploded off the control system; parts list; build sequence.
Module sheets A-101–A-108
A-101Front deskFirst contact
A-102FeasibilityWhere every project starts
A-103EstimatePricing the work
A-104DesignChoosing finishes
A-105BookingHolding the date
A-106Project managementRunning the job
A-107FieldOn site
A-108Edge computeThe technology layer
Configuration sheets A-201–A-205
A-201ADUThe lot tool: address to building envelope to a gated study to a floor-plan playground.
A-202Home remodelThe instant estimate: property-verified and catalog-grounded.
A-203New buildA fixed-price land or site study, or a scoped consult.
A-204CommercialA fixed-price walkthrough or land and site study, booked online, or a scoped consult, then a site meeting and a feasibility retainer in the portal.
A-205VenueA scoped consult; rooms are bookable today.
A-300Room scheduleEvery space Autotelic builds — buildings, the rooms they contain, by purpose; components per room.
A-400Occupancy scheduleWho fills each room and where they book it.
Project
HOW IT WORKS
Sheet
A-100
Sheet title
PLATFORM ASSEMBLY
Rev
2026-09-26
Set
17 SHEETS
Status
RELEASED
123456789
  1. 1Front desk
  2. 2Feasibility
  3. 3Estimate
  4. 4Design
  5. 5Booking
  6. 6Project management
  7. 7Field
  8. 8Edge compute
  9. 9CONTROL SYSTEM
  • Released
  • In progress
  • Not in service
  • Internal — shown, never linked
  • Seat on the base (alignment)
  • Item no. → parts list

Book direct

Autotelic is a Denver design-build-automate contractor run on its own AI platform. This is the drawing set: eight modules, five configurations, and the components inside each one, with what every tool actually does.

Control system

Autotelic runs on a small AI operating layer behind the scenes: a COO Orchestrator that coordinates eleven specialist desks and a rotating set of build desks. The desks each own one lane of the business — the phone line, the site chat, the client portal, labor dispatch, the supplier hub, organic growth, business listings, social publishing, uptime watching, and marketing direction. The build desks are a separate loop: each one picks up a single ticket, works it in its own copy of the codebase, and opens a pull request for a person to review before anything merges. None of this replaces a person’s judgment on money, compliance, or anything destructive — those decisions stay with a person.

Desk schedule

DeskLane
VoiceOwns the phone line — call intake, transcription, and call-intelligence summaries.
ChloeOwns the site's scoping chat and lead capture.
PortalOwns the client portal and the field-ops message flow.
LaborOwns crew labor intake and dispatch for finish work.
SupplyOwns the trade and supplier hub.
GrowthOwns organic growth and the lead pipeline from search.
ListingsOwns business-listing accuracy across directories.
SocialOwns social publishing to the company's own channels.
Fleet OpsWatches the platform's uptime and raises the alarm if something public goes down.
Head of MarketingDirects the marketing lanes and reviews content quality across the other desks.
Build desks (VM 201)The Kimi worktree loop — one ticket in, a branch and a pull request out.

Reviewed artifacts

A build desk opened a fix for a sync bug. The reviewer's first verdict, 21:45: revise — the required test suite failed. The desk fixed the suite. Second verdict, 22:06: approve. Merged at 22:55 the same evening. Two words, twice, and a green check in between: that is the whole gate.
A reviewer verdict on a desk pull request · reviewed 2026-09-08
Issue #458 asked a desk to submit the agent-booking MCP server to a free directory. Desk 2 read the repo's rules first ("this repo owns the public discovery surfaces; this task must not change /estimate or /design"), added four files, ran its own verification script, and opened the pull request with the run log attached. Reviewed and merged the same evening.
A merged desk pull request · reviewed 2026-09-08

The one-day clock

  1. 02:30 Trade knowledge writes (daily)
  2. 03:00 Citation checks (daily)
  3. 03:15 City code-facts harvest (daily)
  4. 04:00 Monday keyword-ranking sync (weekly)
  5. 04:00 Sunday content-packages plan (weekly)
  6. 04:15 Pending call summaries (daily)
  7. 04:30 Content packages build (daily)
  8. 04:45 Power recovery (daily)
  9. 05:30 Grounded content cycle (daily)
  10. 05:45 Content triage (daily)
  11. 06:00 Monday review monitor (weekly)
  12. 06:05 Content learning pass (daily)
  13. 06:30 Monday indexing promotion (weekly)
  14. 07:00 Search Console sync (daily)
  15. 07:00 Monday weekly scorecard (weekly)
  16. 07:15 Lead re-forward sweep (daily)
  17. 07:35 Expired-holds digest (daily)
  18. 17:00 Team-call recap (the COO digest) (daily)
  19. every 15 minutes Municipal code refresh (interval)
  20. every 2 hours Build-desk PR pulse (interval)
  21. every 5 minutes Fleet watch (interval)
  22. every 5 minutes Blog scheduled publish (interval)
CALL NOWBOOKINSTANT ESTIMATE