← Back to overview
demo project · e-scooter, L1e-b class

Watch it hold the why.

One project, from a three-sentence brain-dump to a merged, signed-off baseline. Every screen below is the running product — not a mockup, and not a customer's data.

Book a demo → See the full lifecycle
What is live

Define is live today.

Pick a stage — the film and the walkthrough both follow it. Define is shipped and working. The other four are sequenced behind it, each one building on the data this stage creates.

// Nothing here is a roadmap slide. If a stage is not live, it says so.

    ▸ Read it instead — all twelve beats
    1. 0:00 CoverTwo lines of the thesis land over the drifting graph texture; the wordmark signs it
    2. 0:06 GapA recorded requirement card sits beside an empty dashed rationale card that keeps pulsing
    3. 0:14 CharterThe charter draft is revealed and the low-confidence banner is ringed and spotlit
    4. 0:22 Read onlyThe mainline header strip wipes in and the READ ONLY chip is ringed
    5. 0:28 RejectedThe two rejected alternatives, with one ring sliding from the first reason to the second
    6. 0:38 AuditorThe auditor panel lands, then the capture-quality column insets below it
    7. 0:46 ProposesThe AI suggestion card arrives; rings hit the confidence badge, then the accept/reject row
    8. 0:54 OverruledThe engineer quote holds while the rejection reason is ringed in the shot
    9. 1:04 GraphThe stakeholder graph wipes open left to right so the five concern edges appear to draw
    10. 1:12 GapsThe uncovered-concern chips are ringed, then the drafted requirement confidence score
    11. 1:20 MergeThe merge dialog arrives and the permanence warning is ringed
    12. 1:28 CloseDark teal close: DEFINE live, the four roadmap phases step in, the url resolves

    Recorded, attributed, and linked.

    1. The Record Decision dialog in sysen.ai, showing a decision with two rejected alternatives each carrying its own reason
      fixed pack, swap stations — each with a reason it was rejected
      01«define» · decisions

      Both roads not taken. And why each one died.

      Two years on, nobody is asking what REQ-114 says. They are asking why you ruled out the swap-station model. Here that answer is not a comment. It is a field.

    2. The decision log in sysen.ai with a capture-quality column and a panel showing provenance, rationale and rejected alternatives
      capture quality · provenance, rationale, rejected alternatives
      01«define» · decisions

      Capture quality is a column.

      Every decision is scored on how much of the reasoning survived. One with no alternatives recorded is visibly incomplete — to you, and to the auditor. You cannot quietly skip the part that matters.

    3. AI-elicited stakeholder proposals in sysen.ai, each with a confidence badge, its rationale, and accept, edit and reject actions
      proposed stakeholder · rationale · accept / edit / reject
      02✦ panda · the override

      100% confidence. Still just a proposal.

      PANDA suggests stakeholders, concerns and requirements — with its reasoning attached. Every single one waits on Accept, Edit or Reject.

    4. An engineer rejecting a 100%-confidence AI suggestion in sysen.ai by typing a written reason before confirming
      100% confidence → typed reason → confirm reject
      02✦ panda · the override

      And the engineer can simply say no.

      The rejection is recorded too — who, when, and why — so the disagreement is part of the record rather than a thing that happened in someone's head.

      “I do not think this is an engineering concern to be designed for.”

    5. Graph view in sysen.ai showing one stakeholder node, Urban Commuter, linked by five HAS CONCERN edges to five concern nodes
      one stakeholder node · five has_concern edges
      03«define» · graph view

      Stakeholder → Concern → Requirement.

      Traceability is not a spreadsheet you maintain on the side. It is the shape of the data — so it cannot drift out of date, and it cannot be quietly skipped.

    6. A coverage worklist in sysen.ai listing seven uncovered concerns alongside a drafted requirement with a confidence score
      uncovered concerns (7) · first draft requirement · 99% confidence
      03«define» · coverage

      Seven concerns. No requirement covering them.

      In a document set that hole is invisible — nothing is missing, because nothing was ever supposed to be there. In the graph the requirements lane is simply empty, and the system can hand you the list.

      The rest of the loop

      And the parts you would expect.

      The walkthrough above is what makes this different. The rest is the machinery that makes it safe.

      The Create New Project dialog in sysen.ai with an AI-drafted charter and a low-confidence warning banner

      Charter

      Three sentences of plain English in; objectives, scope and success criteria out — with a banner that tells you when the assistant was not confident.

      The Workspaces screen in sysen.ai showing mainline open in read-only mode

      Branch

      Mainline is read-only. Every change — yours or the machine's — happens on a workspace, so the source of truth is never edited in place.

      The merge-to-mainline confirmation dialog in sysen.ai warning that merging is permanent and cannot be undone

      Review & merge

      Thirty changes, approved item by item by named humans, promoted in one act. Then it is permanent — and who approved what is part of the record.

      See it on your requirements.

      Bring your requirements set to a 30-minute demo. We'll show you the traceability graph it builds.

      Book a demo → Read the vision