Autolace turns a spoken idea into a versioned product brief with an explicit assumption ledger, while the screen assembles the client's product around the conversation. This page is how it works, end to end.
Discovery is scored against a fixed list of sections, and the list is data rather than something written into a screen, so it can be re-derived after more real sessions without a release. Every section carries two names: the one an operator reads, and the one a client reads.
The section list lives in the app's own records, not in this page, so it stays true when a section is added. Sign in to read the list this app is running on right now.
The interview stops on coverage, not on a feeling. It ends when three things hold at once: at least three rounds are complete, the number of BLOCKING ledger entries is at or under the configured threshold, and the last round added less than the configured share of new coverage. Five rounds is the normal cap; a sixth exists only when the specific unknowns it is buying can be named. If they cannot be named, the session is finished.
Every decision made that nobody was asked about is written down as one plain line. Entries carry a kind (taken as read, still to decide, needs a definition, a limit you named, or two answers disagreeing) and a blocking flag for the ones a builder genuinely cannot proceed without. Overriding an entry never deletes it: the correction is a new entry and the original stays beneath it, legible.
One authenticated endpoint serves an engagement's bundle by build code. It is a machine door: no person's session reaches it, and a signed-in operator's browser cannot call it without the factory token.
curl -H "Authorization: Bearer $FACTORY_EXPORT_TOKEN" \ https://your-autolace-host/api/export/HRB-4K2M
There are exactly two outcomes. Either the bundle, which is the engagement, the latest brief version and its sections with provenance, the full ledger including superseded entries, the glossary, the named outside systems and the transcript, or a refusal naming precisely what is missing. Never a partial. The envelope carries a format_version so the payload can grow without breaking a caller.
20 features, 21 declared routes and 31 tables. The list below is not written on this page: it is regenerated from the build's own records, so it says what this build actually promised rather than what somebody remembered.
Rendered from docs/PRD/20-features/ and docs/semantic-layer.json, word for word.
As an operator I can create an engagement for a client and get a short speakable build code so that the call has a record from minute one and a build machine can fetch it later by code.
Lives at/engagements/engagements/new/engagements/[id]
engagementsbuild_codesmembershipsuserssessionsbrief_versionsengagementsbuild_codesmembershipsactivity_eventsaudit_logsAs an operator I can run a model-led interview whose rounds are generated from the accumulating brief so that the questions are about the client's business, never about software in general.
Lives at/api/sessions/[id]/round/engagements/[id]/session/[sessionId]
sessionsroundsanswersledger_entriescoverage_sectionsbrief_sectionsapp_settingsroundsledger_entriescoverage_sectionssession_eventsjobsactivity_eventsAs a client I can land in a conversation that progressively becomes a workspace showing my product so that discovery feels like construction rather than paperwork.
Lives at/engagements/[id]/session/[sessionId]
sessionsroundsanswersledger_entriescoverage_sectionsbrief_sectionsdiagramsactivity_eventsactivity_eventssession_eventsAs a client I can answer one round at a time in cards that teach me which axes exist so that choosing is cheaper than composing and the format never traps me.
Lives at/engagements/[id]/session/[sessionId]
roundsanswerssessionsapp_settingsanswersactivity_eventssession_eventsAs a client I can see every decision the model is making unasked, and override any of them so that an unasked question stops being a silent risk and becomes a visible one.
Lives at/engagements/[id]/session/[sessionId]
ledger_entriesroundssessionsglossary_termsledger_entriesactivity_eventssession_eventsAs an operator I can see at a glance which brief sections discovery still owes so that I can tell whether we are done without guessing.
Lives at/engagements/[id]/session/[sessionId]
coverage_sectionssessionsbrief_sectionscoverage_sectionssession_eventsAs an operator I can end a session holding a brief a build factory can act on so that the call produces the deliverable, with no write-up afterwards.
Lives at/engagements/[id]/brief/engagements/[id]/brief/[version]
briefsbrief_versionsbrief_sectionsledger_entriescoverage_sectionssessionsbriefsbrief_versionsbrief_sectionsactivity_eventssession_eventsAs a client I can watch a diagram of my product assemble as I answer so that I catch a wrong assumption as a shape, in the moment, instead of finding it in a document nobody read.
Lives at/engagements/[id]/session/[sessionId]
diagramsbrief_sectionssessionsroundsdiagramssession_eventsactivity_eventsAs an operator I can see what the session is doing behind the conversation so that the system feels alive and the client can watch it work.
Lives at/engagements/[id]/session/[sessionId]
activity_eventssessionsactivity_eventsAs a client I can name the outside systems my product talks to, in my own words so that a niche vendor gets named while I am still in the room, instead of surfacing after everyone has left.
Lives at/engagements/[id]/session/[sessionId]/engagements/[id]/integrations
named_integrationssessionsengagementsnamed_integrationsactivity_eventssession_eventsAs an operator I can choose which provider and model powers discovery so that the model is a setting, not a constant baked into the code.
Lives at/admin/model
app_settingsapp_settingsaudit_logsAs an operator I can see every engagement and its state in one place so that I can find any client's session without hunting.
Lives at/admin/engagements
engagementssessionsbrief_versionsbuild_codesusersmembershipsaudit_logsAs an operator I can invite a client and assign their role so that nobody self-serves and there is exactly one way in.
Lives at/sign-in/sign-up/admin/invites
invitesusersmembershipsinvitesusersmembershipsaudit_logsnotificationsAs an operator I can resume any session from any client so that a dropped call or a closed laptop never costs the session.
Lives at/engagements/[id]/session/[sessionId]
sessionsroundsanswersledger_entriesactivity_eventscoverage_sectionssessionsactivity_eventssession_eventsAs an factory build machine I can fetch an engagement's bundle by build code so that a build can pick up the intake without anyone coupling to this app's database.
Lives at/api/export/[buildCode]
engagementsbuild_codesbriefsbrief_versionsbrief_sectionssessionsroundsanswersledger_entriesnamed_integrationsaudit_logsnotificationsAs an operator I can download the brief as markdown so that the artifact travels by hand when the machine door is not the right one.
Lives at/engagements/[id]/brief
briefsbrief_versionsbrief_sectionsledger_entriesaudit_logsjobsAs an operator I can see round counts, ledger lengths and exit reasons across real sessions so that the ledger-length threshold gets derived from real briefs instead of guessed.
Lives at/admin/instrumentation
session_metricssession_eventssessionssession_eventsAs an operator I can have invitations and session events reach people by email so that an invited client can actually get in, and nobody has to be told verbally that something finished.
Lives at/settings/notifications/api/notifications
notificationsusersengagementsnotificationsaudit_logsAs an visitor I can read the privacy policy and terms so that the app that holds a client's unreleased product idea says plainly how it treats it.
Lives at/legal/privacy/legal/terms/settings/account
usersmembershipsengagementsbriefsbrief_versionsbrief_sectionssessionsroundsanswersledger_entriesnamed_integrationsusersmembershipsjobsaudit_logsAs an visitor I can understand what Autolace is before I ever sign in so that a prospective client who is sent a link arrives somewhere that explains itself.
Lives at/
A declared route is a built route. This is the whole list, with the tables each one works with; the feature column links back to what lives there.
| Route | Feature | Data it works with |
|---|---|---|
/ | FeatureF20 | Data it works withnothing stored |
/admin/engagements | FeatureF12 | Data it works withaudit_logsbrief_versionsbuild_codesengagementsmembershipssessionsusers |
/admin/instrumentation | FeatureF17 | Data it works withsession_eventssession_metricssessions |
/admin/invites | FeatureF13 | Data it works withaudit_logsinvitesmembershipsnotificationsusers |
/admin/model | FeatureF11 | Data it works withapp_settingsaudit_logs |
/api/export/[buildCode] | FeatureF15 | Data it works withanswersaudit_logsbrief_sectionsbrief_versionsbriefsbuild_codesengagementsledger_entriesnamed_integrationsnotificationsroundssessions |
/api/notifications | FeatureF18 | Data it works withaudit_logsengagementsnotificationsusers |
/api/sessions/[id]/round | FeatureF2 | Data it works withactivity_eventsanswersapp_settingsbrief_sectionscoverage_sectionsjobsledger_entriesroundssession_eventssessions |
/engagements | FeatureF1 | Data it works withactivity_eventsaudit_logsbrief_versionsbuild_codesengagementsmembershipssessionsusers |
/engagements/[id] | FeatureF1 | Data it works withactivity_eventsaudit_logsbrief_versionsbuild_codesengagementsmembershipssessionsusers |
/engagements/[id]/brief | FeatureF7F16 | Data it works withactivity_eventsaudit_logsbrief_sectionsbrief_versionsbriefscoverage_sectionsjobsledger_entriessession_eventssessions |
/engagements/[id]/brief/[version] | FeatureF7 | Data it works withactivity_eventsbrief_sectionsbrief_versionsbriefscoverage_sectionsledger_entriessession_eventssessions |
/engagements/[id]/integrations | FeatureF10 | Data it works withactivity_eventsengagementsnamed_integrationssession_eventssessions |
/engagements/[id]/session/[sessionId] | FeatureF2F3F4F5F6F8F9F10F14 | Data it works withactivity_eventsanswersapp_settingsbrief_sectionscoverage_sectionsdiagramsengagementsglossary_termsjobsledger_entriesnamed_integrationsroundssession_eventssessions |
/engagements/new | FeatureF1 | Data it works withactivity_eventsaudit_logsbrief_versionsbuild_codesengagementsmembershipssessionsusers |
/legal/privacy | FeatureF19 | Data it works withanswersaudit_logsbrief_sectionsbrief_versionsbriefsengagementsjobsledger_entriesmembershipsnamed_integrationsroundssessionsusers |
/legal/terms | FeatureF19 | Data it works withanswersaudit_logsbrief_sectionsbrief_versionsbriefsengagementsjobsledger_entriesmembershipsnamed_integrationsroundssessionsusers |
/settings/account | FeatureF19 | Data it works withanswersaudit_logsbrief_sectionsbrief_versionsbriefsengagementsjobsledger_entriesmembershipsnamed_integrationsroundssessionsusers |
/settings/notifications | FeatureF18 | Data it works withaudit_logsengagementsnotificationsusers |
/sign-in | FeatureF13 | Data it works withaudit_logsinvitesmembershipsnotificationsusers |
/sign-up | FeatureF13 | Data it works withaudit_logsinvitesmembershipsnotificationsusers |
Nobody self-serves. An operator invites an address and decides its seat before the account exists. A brand-new account holds a client seat with no engagements attached, and sees an empty state naming its operator until one is.
Which means an account made to look around opens onto nothing. Two seats into the seeded world are published on the demo page for exactly that reason.
Write to Pisteyo through the support form. A person reads it and answers within one business day. What happens to session content, who processes it and how long it is kept are all set out in the privacy policy, and who owns the brief is the first clause of the terms.