Essai 01 coverage
All 32 use cases have a substantive first version in one flat collection. This completes Essai 01 under Lawrence’s stated criterion, not every use case’s full ambition or its empirical validation. No live model, authenticated collaboration or closed-browser notification service is connected.
| ID | First version | Current mode | Wider ambition or limit |
|---|---|---|---|
| 1.1 | Which account applies? | Local retrieval and register | Live evidence-grounded AI retrieval and answers over a real, maintained corpus remain open. |
| 1.2 | Whose outcome? | Local relationship model | The weights are workshop judgements. Shared stewardship and evidence of useful decisions remain untested. |
| 1.3 | A connection has a kind | Local typed network | Real evidence stewardship, attribution and usefulness remain untested; a plotted position is not influence. |
| 1.4 | The constraint moves | Local numerical model | The resource budgets and coefficients are invented. This is neither an executable timetable nor a validated investment appraisal. |
| 2.1 | A trial worth having | Local trial register | The records do not authenticate participation or establish that an adoption choice is worthwhile. |
| 2.2 | A signal worth seeing | Local calculated signals | The signal definitions and thresholds are local assumptions; useful warning performance remains unmeasured. |
| 2.3 | Small enough to agree | Local workspace and recorded proposals | Live AI co-creation, authenticated simultaneous collaboration and trusted attribution remain open. |
| 2.4 | Keep the recipe | Local workbench and recorded/imported outputs | In-app live AI execution and independent evidence of reliable prompt reuse remain open. |
| 3.1 | What applies here? | Local rule-based tailoring | The rule vocabulary is small and invented. Real framework coverage and evidence adequacy are not established. |
| 3.2 | A route that fits | Local options model | Scores express chosen priorities; the invented constraints are not an approved procurement or engineering framework. |
| 3.3 | A meeting with a decision | Local assembly and recorded AI example | Live AI drafting, prior-action feeds, circulation and measured preparation/checking savings remain open. |
| 3.4 | Checked in what sense? | Local evaluation of supplied outputs | This evaluates supplied outputs on specific cases. It cannot support a universal model ranking or authenticated independent review. |
| 4.1 | Useful elsewhere? | Local illustrative case library | The cases illustrate the evidence-handling method; they provide no empirical proof of infrastructure success factors. |
| 4.2 | Learn from the case | Local rule-based learning exercise | Live conversational coaching grounded in an approved archive and evidence of learning transfer remain open. |
| 4.3 | Ready on the first pass? | Local event-log analysis | Synthetic event logs cannot establish real estimation performance or explain the causes of delay. |
| 4.4 | The missing link | Local rule-backed suggestions | Authored rules expose some candidate dependencies; general AI discovery and complete scheduling remain open. |
| 5.1 | A gate with reasons | Local state machine | Evidence notes are assertions. A simulated status change confers no authority to work on infrastructure. |
| 5.2 | What is in the tables? | Local data profiling | Inferred types and candidate joins do not establish business meaning. Database connections are outside this local profiler. |
| 5.3 | Make retreat possible | Local experiment workflow | This is a bounded office-process exercise. Its fallback simulation is not an operational recovery plan. |
| 5.4 | What did the task list miss? | Local typed-vocabulary traversal | Typed traversal is not a complete industry ontology, a formal reasoner or a proof of scope completeness. |
| 6.1 | A draft is not a gate | Local assembly and recorded AI example | Live AI drafting and independently validated evidence review remain open. Approval stays outside this drafting tool; local review cannot advance a gate. |
| 6.2 | Try one office job | Local recipe practice and external handoff | The page cannot inspect or execute work in an office tenant. External execution needs the appropriate authorised integration. |
| 6.3 | Keep the disagreement | Local facilitated graph | Local facilitation and file exchange do not provide simultaneous collaboration or causal inference. |
| 6.4 | Remember before deciding | Local lesson retrieval and review | Live AI lesson review, authenticated team capture and closed-browser notifications remain open. |
| 7.1 | Find the story in the pattern | Local participant-rated landscape | Participant positions are explicit judgements, not psychological measurements or inferred dispositions. |
| 7.2 | The work of getting better | Local stock-flow simulation | The stock-flow coefficients and uplift are assumed. No real time saving, adoption or service improvement is established. |
| 7.3 | Practise on the artefact | Local editing and data exercise | Practice checks apply only to this exercise. Cross-application coaching and live contextual AI remain open. |
| 7.4 | What does that number mean? | Local metric/schema model | The schema exposes assumptions; an arrow does not perform an aggregation or establish causal influence. |
| 8.1 | Know now, act later? | Local sequential-policy simulation | Policies are supplied, not learned or proved optimal. The scenario is invented and cannot determine safe real-world action. |
| 8.2 | The shape of waiting | Local dated-record analysis | A duration is not a diagnosis; summed decision-days are not elapsed project time or decision quality. |
| 8.3 | Spend attention carefully | Local rules-based triage | Explicit rules do not provide validated NLP assurance. Severe-case recall, real review quality and human benefit remain untested. |
| 8.4 | The shared dependency | Local typed-path analysis | Typed paths suggest interactions to investigate; they are not probabilities or established causes. |
The original private document and detailed method remain in the foray folder. All public sources and data are invented unless an app names a primary method/platform reference. The standalone Experiments site retains all previous routes. Main-site integration is outside this work.