Stand up the practice
Shop that has Archi, or will install it, and has not run the orchestrator on their hosts.
Bridge on loopback, skills discovered, one View Plan approved or rejected, no requirement to write model content.
Engagement
JG Systems Consulting Ltd will stand the pack up on your hosts, produce a named viewpoint in your Archi model, or train the people who will keep running /archi-orchestrator.
The skills stay MIT. This page is the firm's work. You still approve every View Plan. Archi stays on your disk.
§01 · Ways
Three doors
01
02
Delivery work packages
Named concern already on the board. One viewpoint or a short adjacent pair.
Views and traces in their Archi file. Rationale in documentation fields.
03
Enablement
EA or technology architects who will run the pack after the firm leaves.
People who can invoke the orchestrator and a written approve/reject rule. Named review is a third enablement offer, bought on its own.
Pick one door per enquiry. A first modelling run can follow standup.
§02 · Stand up
Stand up the practice
Install JGS Archi Bridge and this pack on the hosts they name. Host paths: docs/other-agents.md.
First /archi-orchestrator call on a non-secret intent, or on a throwaway model. Stop at the View Plan gate. They approve or reject. The firm does not write their architecture unless they also buy a delivery package. Sample asks: How you ask.
Done when: MCP shows Stop MCP Server, skills are visible after an agent restart, they have issued one orchestrator line, and they have approved or rejected the View Plan.
Out of scope here: estate redraw, prompt-card authoring, a production model.
§03 · Delivery
Delivery work packages
One concern, one View Plan, their model on their disk. Extra packages cover extra journeys or an adjacent pair.
| Package | What lands in Archi | Done when |
|---|---|---|
| Motivation pack | Drivers, goals, outcomes. No applications on the canvas | Board can read why the change is on the list |
| Single capability cut | One value stream: capabilities plus the processes and applications that already cover them | Path from a capability through a process to an application |
| Business operations view | Actors, roles, processes, services for one journey | Journey is in Archi |
| Application landscape (bounded) | Components, services, interfaces, overlap for a named estate slice | Overlap visible; no silent duplicates |
| Technology / landing zone | As-is hosts versus target. Business not redesigned | Plateaus exist; no invented business process |
| Migration roadmap | Work packages, gaps, plateaus on a model that already has current and target | Roadmap is in the model |
| Layout and QA only | Relayout plus a compliance report. No new elements | View readable; findings listed |
| Trace stitch | Cross-layer links after two or more views exist | Named concern has a motivation-to-technology chain |
Client supplies a running Archi plus Bridge, or buys standup first. Extra journeys, extra stakeholders, or an unbounded estate are extra packages. Adjacent pair (current versus target plus roadmap) is still a short list of packages, not a programme contract. User governs architectural decisions. Skills stay consume-only toward the Bridge.
§04 · Enablement
Enablement
View Plan clinic
Sponsors and leads practise approve or reject, including what a specialist may write.
They can reject a plan that exceeds the named altitudes.
Method studio
Architects drive the orchestrator on a non-secret scenario. House style, layer cuts, local defect versus upstream defect.
Two or three of them can complete a run to View Plan without the firm at the keyboard.
Named review
Monthly read of their View Plans or a model excerpt. Challenge cut, traces, and scope.
Written comments on the plans they send, on an agreed turnaround.
Public GitHub Issues stay for pack defects every user would hit. Named review is their architecture.
§05 · Enquire
Enquire
Write what you want (standup, a package name from the table, clinic, studio, or named review), which agent hosts you use, and whether Archi plus the Bridge already run.
That form is the door for JGSC Labs and for this firm's modelling work. Discussions stay the public room for worked runs.
§06 · Not sold
What this page does not sell
Paid MIT zip
A paid licence of the MIT zip.
Hosted Archi
Hosted Archi or a model that leaves their machine.
Unbounded estate
Whole-estate partnership with no viewpoint list.
Bridge patches
Plugin patches or pull requests against jgs-archi-mcp.