---
path: /studio/isis/event-publisher
surface: studio
domain: isis
auth:
  signed-in + studio entitlement; Studio Isis production boundary hard-blocks
  this AAA-only route. Automated lane verification uses the explicit
  localhost-only E2E bypass.
source: apps/oshun/web/src/app/studio/isis/event-publisher/page.tsx
status: walked
last_walked:
  '2026-07-23 automated desktop Chromium + Pixel 7 mobile walk — production
  hard-block, localhost-only lane entry, explicit composition boundary, four
  child lanes, absence of an aggregator request, route status, touch targets,
  responsive containment, and applicable axe verified'
---

# Isis Event Publisher

## Purpose

UI-only, non-authoritative composition of four independent Isis workspaces:
Integration Events, Workflow Registry, Generation API, and Output Registry. Each
child retains its own exact contract and state. The composition has no Event
Publisher endpoint, retained topic/stream/delivery state, publication or retry
action, receipt/evidence authority, parity run, governance record, or release
decision.

## Entry points

- Quick-action card from embedded-lane routes
- Studio index (`/studio`)
- Direct URL / bookmark (AAA-gated)

## Layout regions

- **Breadcrumb panel** (`data-isis-event-publisher-breadcrumbs`): Studio →
  Integration Events → (current)
- **Workspace panel** (`data-isis-event-publisher-workspace`):
  - `<h1>` "Isis Event Publisher Workspace"
  - Honest summary and exact
    `ui_only_non_authoritative_embedded_lane_composition` disposition
  - **Composition Boundary** with four cards: independent lane authority, no
    publisher endpoint, no publication/delivery/evidence authority, and no
    governance/release authority
  - Four embedded lanes: Integration Events, Workflow Registry, Generation API,
    and Output Registry
- **Route map panel** (`data-isis-event-publisher-route-map`): one
  `mounted-composition` and five `documented-contract` entries
- **Quick-actions panel**: links to Integration Events, Workflow Registry,
  Output Registry, and Studio

## States

No fetch at the composition level. Each child lane manages its own loading,
unauthorized, error, ready, and result states.

- [ ] **Integration Events Lane** — see
      [`studio-isis-integration-events.md`](./studio-isis-integration-events.md)
- [ ] **Workflow Registry Lane** — see
      [`studio-isis-workflow-registry.md`](./studio-isis-workflow-registry.md)
- [ ] **Generation API Lane** — see
      [`studio-isis-generation-api.md`](./studio-isis-generation-api.md)
- [ ] **Output Registry Lane** — see
      [`studio-isis-output-registry.md`](./studio-isis-output-registry.md)
- [ ] **Gated** — the Event Publisher route is production-hard-blocked

## Interactions

### Composition boundary

- [ ] **Boundary cards** ×4 — non-interactive and authority-limiting

### Embedded lanes

- [ ] Integration Events / Workflow Registry / Generation API / Output Registry
      — walk each in its own doc

### Route Map

- [ ] **Mounted composition** ×1
- [ ] **Documented route shapes without pages or authority** ×5

### Quick-actions

- [ ] **Open Isis Integration Events workspace** →
      `/studio/isis/integration-events`
- [ ] **Open Isis Workflow Registry workspace** →
      `/studio/isis/workflow-registry`
- [ ] **Open Isis Output Registry workspace** → `/studio/isis/output-registry`
- [ ] **Back to Studio workspace index** → `/studio`

## Data & contracts

- **Reads / writes**: none from this composition directly; delegated to child
  lanes under their own exact contracts
- **Publisher state**: no topic, stream, delivery, retry, receipt, diagnostic,
  parity, or governance record
- **Operations**: no publish, retry, delivery, receipt, remediation, permission,
  audit, certification, approval, or release action
- **Realtime**: none
- **Auth**: AAA-gated Studio route behind the signed-in + studio proxy gate;
  embedded lanes are individually admin-scoped and fail closed
- **Component sources**:
  - `apps/oshun/web/src/components/studio/StudioIsisEventPublisherWorkspace.tsx`
  - `apps/oshun/web/src/components/studio/StudioIsisEventPublisherRouteMap.ts`

## Cross-references

- Studio overview: [`../../studio-overview.md`](../../studio-overview.md)
- Embedded lanes:
  - [`studio-isis-integration-events.md`](./studio-isis-integration-events.md)
  - [`studio-isis-workflow-registry.md`](./studio-isis-workflow-registry.md)
  - [`studio-isis-generation-api.md`](./studio-isis-generation-api.md)
  - [`studio-isis-output-registry.md`](./studio-isis-output-registry.md)

## Open questions / known gaps

- [ ] Topic, stream, diagnostics, parity, and governance paths are documented
      shapes only, with no pages or corresponding aggregator authority
- [ ] There is no standalone Event Publisher, retained delivery/retry store,
      receipt/evidence record, parity certification, governance, approval, or
      release authority here
- [ ] The Integration Events child only dry-run validates envelopes; no actual
      bus publish path is exercised from this composition