Each component of the workspace, as the vendor’s team sees it. Same world as the demo: one software vendor, four hospital customers, and work item ARN-608 — par-level forecasting — where it applies.
Every customer: their grants, the state of their digest, and open work. All of Arena’s data is scoped to an account.
What Arena holds about one customer, with the source of each line. Updated as new exports, calls, and filings arrive.
The vendor’s repository, indexed: each path, what it does, which customers run it — including deprecations and the cost of past forks.
ARN-608’s requirements against the index above, checked before the proposal was sent: three covered by existing modules, one gap routed to the platform backlog.
Chosen by the customer, source by source, in their portal. This panel is the vendor’s view. Reads are logged on the customer’s side; every grant is revocable.
Signals derived from the customer’s own meetings go to their owner alone. Each item is declined, edited, or approved; the vendor receives only approved items, marked as such.
Opportunities Arena discovered from each account’s digest and the vendor’s own codebase, ranked by return. A customer sees one only after the vendor’s owner reviews and sends it.
One record per opportunity: proposal, threads, sign-off, ticket, pull request, approvals. This is ARN-608 — the one the demo follows.
Requests customers send run through the same pipeline — scoped, cited, built, recorded. A request matching something already shipped surfaces the match; the engineer chooses.
Per-customer configuration. On: live for that customer. Off: never shipped to them. Switching off is the rollback — one action, on the record.
| CHANGE | ORIGIN | CUST. A | CUST. B | CUST. C | CUST. D |
|---|---|---|---|---|---|
| par-forecasting | ARN-608 · Aug 12 | ||||
| count-scheduling | ARN-489 · Jun 30 | ||||
| expiry-reports | platform · 2025 |
Per customer: every grant, thread, decision, approval, deploy, and rollback — dated and cited. Queryable; answers carry their sources.
Arena runs digest, scoping, discovery, and drafts. Lena sends proposals; Jonas approves pull requests; the customer approves scope and previews.