Engineering knowledge as infrastructure

Engineering context

Every engineered solution has a context: the problems it addresses, the intentions behind it, its requirements, the decisions, assumptions and trade-offs that shaped it, its models, its implementation, how it was validated, the evidence gathered, and how all of these relate. When that context is structured, persistent, scoped to the solution and aware of versions, a team can analyze the impact of a change before making it and reconstruct the reasons for a past decision long after the people involved have moved on.

Studio is the platform for that context. It lets teams organize engineering artifacts as records, maintain typed traceability between them, preserve their history in revisions and baselines, and access that knowledge through the browser and, optionally, through MCP tools that read and, for people allowed to, draft records, without ever approving them.

An independent method: ESEM

The Explicit Software Engineering Method (ESEM), authored by rafageist, addresses the same concern from a different angle. It is a method, not a tool: a process-orthogonal set of obligations for making engineering reasoning, such as intent, decisions, assumptions, trade-offs and validation, explicit, traceable and evaluable, whatever process a team follows.

The two are independent. ESEM does not require Studio, and Studio does not require ESEM: a team can use Studio with the Unified Process alone, or apply ESEM with other tools. Where they meet, Studio's records, traces, revisions and evidence can hold what a team following the method makes explicit. An optional evaluator for ESEM obligations is a roadmap item; Studio does not evaluate or enforce the method today.

Studio also runs alongside the tools developers already rely on (IDEs, Git, CI pipelines and trackers) and connects to them instead of replacing them.

1. Engineering records & traceability Available

   Records with types, codes, lifecycles and revisions, including decisions, risks and evidence; typed, revisioned and access-aware traces; [[CODE]] links with backlinks.

2. Diagram modelers Available

   The modeler platform with BPMN (bpmn-js) and UML (PlantUML in the browser), element links to records and diagrams embedded in text.

3. Unified Process Available

   Developments, phases, iterations, milestones, activities, work products, development cases, advisory readiness, change requests and baselines.

4. Validation, knowledge and coordination Available

   Test management with frozen runs, evidence and QA issues; knowledge base and discussions on every record; projects, Kanban boards and timesheets.

5. Code, documentation & databases Available

   Code Source indexed from Git, code documentation from any language, database schema snapshots with explorer and evolution, and an optional MCP server for AI assistants.

6. Installation & updates Available

   A branded web installer on Drupal 11.4 with the MCP integration as an option, and a base recipe that adds Studio to an existing Drupal site and updates sites already running it.

7. Hardening & releases Next

   Domain-integrity fixes from the consolidation audit, isolated install and upgrade tests, contribution guidelines and a versioned release and upgrade policy.

   Studio issues #4–#20, #34–#37

8. Engineering context delivery Planned

   An explicit contract for the context of a Development (identity, scope, versions, provenance and access), then bounded, reproducible context views for people and for MCP clients. Deterministic assembly from recorded knowledge, no dependency on a language model.

   Studio issues #38, #39

9. Engineering Discovery Planned

   Investigations with questions, answers, evidence and conclusions, linked to Unified Process records.

   Studio issue #27

10. Modeling Foundation Planned

    A semantic model repository and metamodel extension contract, distinct from today's diagram documents, with language extensions for UML, BPMN, IFML, ArchiMate, DMN and CMMN.

    Studio issues #45–#51

11. Semantic knowledge, concept maps & UI modeling Planned

    Curated concepts and propositions, concept maps as views of them, a UI modeler for interface and form design, and a bridge between UI components and IFML interaction models.

    Studio issues #40–#43

12. Engineering intelligence Planned

    Development Pulse and database analytics, UML generated from process and schema records, code quality findings, automated test evidence and an OpenAPI explorer.

    Studio issues #28–#32

13. Optional ESEM evaluator Design first

    A pluggable, optional evaluator of method obligations against a Development's versioned context, never a mandatory workflow. It waits on the maturity of the method's rules and on the engineering context contract.

    Studio issue #56