Mixed freshness. Depending on the panel, rows here are read live from elisa-core or come from a frozen copy of ELISA’s local store taken on 22 October 2026 — each panel says which, underneath itself. No agent is running.

ELISAOperations
Connecting

Assets & Artifacts

Sources, drafts, versions and final operations packages — with the original source never overwritten.

Nothing here yet

Sources, drafts, versions and final operations packages — with the original source never overwritten.

The backend for this is still being built.

Technical detail
  • GET /api/assets
  • GET /api/assets/:assetId/artifacts

This sector’s fleet

Real rows from elisa.db, scoped to this sector’s own agents — not the business surface above, which this sector does not yet have rows for.

Agents (7)

  • Orchestrator · Operations orchestration

    The only agent that accepts, rejects or splits an operations work package, and the only one that assigns operations jobs.

    operations.orchestrator
    0 skillsIdle — nothing queued
  • Agent 1 · Project & task flow

    Breaks an approved objective into milestones, tasks, dependencies, owners and acceptance criteria, and is the single author of the project and task records.

    operations.agent_1
    1 skillIdle — nothing queued
  • Agent 2 · SOP, capability & capacity

    Writes and versions the SOP for work that has actually been done twice, and keeps the capability and capacity map honest.

    operations.agent_2
    1 skillIdle — nothing queued
  • Agent 3 · Vendors, issues & delivery quality

    Runs vendor discovery and evaluation, drives issues to a closure with a known root cause, and owns the delivery review record.

    operations.agent_3
    2 skillsIdle — nothing queued
  • Agent 4 · Scheduling & commitments

    Owns the calendar as a commitment record: what was promised to whom, by when, and whether the slot still exists.

    operations.agent_4
    0 skillsIdle — nothing queued
  • Agent 5 · Documentation & record custody

    Keeps the written record complete and findable — runbooks, the artifact and evidence index, and custody of the files a job produced.

    operations.agent_5
    0 skillsIdle — nothing queued
  • Agent 6 · Tooling & dependency register

    Maintains the honest register of what the fleet depends on — connectors, MCP servers, tool policies, external services — and whether each is actually wired.

    operations.agent_6
    0 skillsIdle — nothing queued

7 rows · agents, agent_status_cache · read 2026-10-25T19:16:45.004Z

Skills (4)

4 distinct skills held in this sector — out of 262 in the catalogue fleet-wide.

  • note-taking×1
  • productivity×1
  • research×1
  • web×1

4 rows · agent_skills ⋈ skills, scoped to this sector · read 2026-10-25T19:16:45.004Z

Lessons (16)

7 binding (L0, enforced at the tool call) and 9 advisory (L1) in this sector — 40 of 155 are binding fleet-wide.

Binding — L0

  • operations.calendar.invitee.approvalaccepted

    A calendar write that reaches another person needs an approval token first.

    Scheduling & commitments · agent · confirmed 1×
  • operations.never.delete.stored.fileaccepted

    Never delete, trash or re-share a stored file. Custody adds and reports; it does not remove.

    Documentation & record custody · agent · confirmed 1×
  • operations.no.notion.no.slackaccepted

    Notion and Slack are forbidden. The ERP is the only workspace.

    Project & task flow · agent · confirmed 1×
  • operations.sop.never.overwrittenaccepted

    An SOP change is a new version. The previous version keeps its text and its date.

    SOP, capability & capacity · agent · confirmed 1×
  • operations.never.auto.restoreaccepted

    A missing file is reported, never regenerated or restored without being asked.

    Documentation & record custody · agent · confirmed 1×
  • operations.never.mark.wiredaccepted

    Never mark a connector connected or a tool policy allowed. Propose it; a human arms it.

    Tooling & dependency register · agent · confirmed 1×
  • operations.never.touch.secretsaccepted

    Never read, write or echo a credential, token or key, and never touch credential_grants.

    Tooling & dependency register · agent · confirmed 1×

Advisory — L1

  • operations.no.unbuilt.assignmentaccepted

    Never assign work to an agent that dispatchable() refuses. A registry record is not a worker.

    Operations orchestration · agent · confirmed 1×
  • operations.people.boundaryaccepted

    A People + HR record may be referenced by id and never reproduced in an operations artifact.

    Operations orchestration · agent · confirmed 1×
  • operations.acceptance.criteria.requiredaccepted

    Never create a project or task record whose acceptance criteria are empty.

    Project & task flow · agent · confirmed 1×
  • operations.sop.needs.two.runsaccepted

    Never author an SOP version for work with fewer than two completed job records.

    SOP, capability & capacity · agent · confirmed 1×
  • operations.issue.root.cause.requiredaccepted

    Never close an issue with an empty root cause.

    Vendors, issues & delivery quality · agent · confirmed 1×
  • operations.no.commitmentaccepted

    Evaluate and recommend. Never commit, order, sign or accept a vendor quote.

    Vendors, issues & delivery quality · agent · confirmed 1×
  • operations.calendar.unwiredaccepted

    If the calendar connector is not registered, the job is blocked. Do not report a schedule you could not read.

    Scheduling & commitments · agent · confirmed 1×
  • operations.calendar.invitee.approvalaccepted

    A calendar write that reaches another person needs an approval token first.

    Scheduling & commitments · agent · confirmed 1×
  • operations.never.delete.stored.fileaccepted

    Never delete, trash or re-share a stored file. Custody adds and reports; it does not remove.

    Documentation & record custody · agent · confirmed 1×

16 rows · agent_lessons, scoped to this sector · read 2026-10-25T19:16:45.005Z

SOP (1)

  • operations.objective_to_delivery · v1active

    Seeded from the spec's step list.

    Body
    # SOP: Objective To Delivery

Source: D:\ELISA\ELISA_WORKFLOWS_SOPS.md, verbatim step list. Seeded 2026-10-20.

## Steps

1. Approved objective becomes a project record.
2. Agent 1 creates milestones, tasks, dependencies, owners, and acceptance criteria.
3. Agent 2 maps capability/capacity and maintains the SOP for repeated work.
4. Agent 3 handles vendor actions, issues, risks, and quality review.
5. Delivery review records what worked, what failed, and what should change in the SOP.

1 row · sop_versions, scoped to this sector · read 2026-10-25T19:16:45.006Z

Memory (14)

14 memory rows.

  • charter.1fact

    An empty operations queue stays empty. Idle is a state, not a prompt to invent work.

    Operations orchestration · recall 1 · weight 100
  • charter.2fact

    Six specialists, one owner per record type. If two could do it, the orchestrator picks one and says why.

    Operations orchestration · recall 1 · weight 99
  • charter.1fact

    A task with no acceptance criterion is a wish. Refuse the breakdown rather than guess the done-condition.

    Project & task flow · recall 1 · weight 100
  • charter.2fact

    Deepak's plans use Day N from kickoff, never calendar dates.

    Project & task flow · recall 1 · weight 99
  • charter.1fact

    An SOP for work done once is fiction. Two completed runs, or no SOP.

    SOP, capability & capacity · recall 1 · weight 100
  • charter.2fact

    A capability map is a record of what was done, never a copy of what a registry row claims.

    SOP, capability & capacity · recall 1 · weight 99
  • charter.1fact

    Vendor selection ends at a recommendation. Money is a finance record and finance is locked.

    Vendors, issues & delivery quality · recall 1 · weight 100
  • charter.2fact

    An issue closed without a root cause reopens. Record the cause or leave it open.

    Vendors, issues & delivery quality · recall 1 · weight 99
  • charter.1fact

    Every calendar write with an invitee is an outbound message. It needs an approval token, not a judgement call.

    Scheduling & commitments · recall 1 · weight 100
  • charter.2fact

    No MCP server is wired into Hermes yet. A calendar read that cannot run is a blocked job, never an assumed answer.

    Scheduling & commitments · recall 1 · weight 99
  • charter.1fact

    Missing files are curation, not recovery. Report the gap and ask; never auto-restore a deletion.

    Documentation & record custody · recall 1 · weight 100
  • charter.2fact

    Document alongside the work, unasked. An undocumented delivery is an incomplete one.

    Documentation & record custody · recall 1 · weight 99
  • charter.1fact

    Declared is not wired. Every MCP server in this fleet is a requirement with wired=false until a human says otherwise.

    Tooling & dependency register · recall 1 · weight 100
  • charter.2fact

    A declared-but-missing capability is a blocked job, never a silent no-op.

    Tooling & dependency register · recall 1 · weight 99

14 rows · agent_memory, scoped to this sector · read 2026-10-25T19:16:45.005Z

Activity (97)

Showing the latest 30 of 97 events for this sector's agents.

  • 20/10/2026, 13:15:11agent_lesson.promotedDocumentation & record custody
  • 20/10/2026, 13:15:11agent_lesson.candidateDocumentation & record custody
  • 20/10/2026, 13:15:11feedback.recordedDocumentation & record custody
  • 20/10/2026, 13:15:11agent_lesson.retiredDocumentation & record custody
  • 20/10/2026, 13:15:11agent_lesson.promotedScheduling & commitments
  • 20/10/2026, 13:15:11agent_lesson.candidateScheduling & commitments
  • 20/10/2026, 13:15:11feedback.recordedScheduling & commitments
  • 20/10/2026, 13:15:11agent_lesson.retiredScheduling & commitments
  • 20/10/2026, 13:13:47agent_lesson.repeatDocumentation & record custody
  • 20/10/2026, 13:13:47feedback.recordedDocumentation & record custody
  • 20/10/2026, 13:13:47agent_lesson.repeatScheduling & commitments
  • 20/10/2026, 13:13:47feedback.recordedScheduling & commitments
  • 20/10/2026, 12:40:04agent_lesson.promotedTooling & dependency register
  • 20/10/2026, 12:40:04agent_lesson.candidateTooling & dependency register
  • 20/10/2026, 12:40:04feedback.recordedTooling & dependency register
  • 20/10/2026, 12:40:04agent_lesson.promotedTooling & dependency register
  • 20/10/2026, 12:40:04agent_lesson.candidateTooling & dependency register
  • 20/10/2026, 12:40:04feedback.recordedTooling & dependency register
  • 20/10/2026, 12:40:04agent_lesson.promotedDocumentation & record custody
  • 20/10/2026, 12:40:04agent_lesson.candidateDocumentation & record custody
  • 20/10/2026, 12:40:04feedback.recordedDocumentation & record custody
  • 20/10/2026, 12:40:04agent_lesson.promotedDocumentation & record custody
  • 20/10/2026, 12:40:04agent_lesson.candidateDocumentation & record custody
  • 20/10/2026, 12:40:04feedback.recordedDocumentation & record custody
  • 20/10/2026, 12:40:04agent_lesson.promotedScheduling & commitments
  • 20/10/2026, 12:40:04agent_lesson.candidateScheduling & commitments
  • 20/10/2026, 12:40:04feedback.recordedScheduling & commitments
  • 20/10/2026, 12:40:04agent_lesson.promotedScheduling & commitments
  • 20/10/2026, 12:40:04agent_lesson.candidateScheduling & commitments
  • 20/10/2026, 12:40:04feedback.recordedScheduling & commitments

97 rows · events, scoped to this sector · read 2026-10-25T19:16:45.006Z