Librarian lane: deploy a fourth community agent on the librarian role #1063

Closed
opened 2026-08-19 08:05:38 +00:00 by coilyco-ops · 3 comments
Member

The librarian roster role now bakes from the community person package under agent/compose/person (see the PR referencing this issue and docs/sirens-echo-person.md). The role exists and its bundle verifies, but no lane composes it yet. Remaining work, in order:

  • A lane definition (agents/<lane>/definition.yaml, packs, probes, evaluations) with its own Discord application and identity. The lane decides response style: role and voice are separate axes.
  • Deployment: SIRENS_ECHO_ROLE=librarian on the new lane's service, SSM config, and the deploy-repo changes. DevOps-owned, handed over rather than done from this task.
  • Eval coverage for the librarian charter (provenance-first retrieval, record-vs-memory conflicts, gap filing) and the identity battery for the new lane.
  • Seat naming review: the package ships Libby (they) as a placeholder-quality default. Rename in review if wanted.

Authored by the AI Engineer seat with Kai steering. The package restates the meticulous, skeptical, and editorial personality bodies verbatim from agent-compose's embedded Core Roster, so a core edit to those three bodies now has a copy here to sync.

The librarian roster role now bakes from the community person package under `agent/compose/person` (see the PR referencing this issue and docs/sirens-echo-person.md). The role exists and its bundle verifies, but no lane composes it yet. Remaining work, in order: * A lane definition (`agents/<lane>/definition.yaml`, packs, probes, evaluations) with its own Discord application and identity. The lane decides response style: role and voice are separate axes. * Deployment: `SIRENS_ECHO_ROLE=librarian` on the new lane's service, SSM config, and the deploy-repo changes. DevOps-owned, handed over rather than done from this task. * Eval coverage for the librarian charter (provenance-first retrieval, record-vs-memory conflicts, gap filing) and the identity battery for the new lane. * Seat naming review: the package ships `Libby (they)` as a placeholder-quality default. Rename in review if wanted. Authored by the AI Engineer seat with Kai steering. The package restates the meticulous, skeptical, and editorial personality bodies verbatim from agent-compose's embedded Core Roster, so a core edit to those three bodies now has a copy here to sync.
Author
Member

Cross-reference: #1062 (filed earlier today by the exec seat) records Kai's librarian idea as a framing decision for the existing Echo lane, with the wording owned by the creator seat and gated on the Sirens admins and the identity eval. This issue is the complementary half: a distinct librarian roster role for a possible fourth lane, baked from the community person package. The two can land independently - #1062 needs no new role, and this role composes no lane until deployment picks one up. If #1062 resolves as 'name Echo the librarian', the fourth-lane build here may become unnecessary and this issue can close with that reason. The PR adding the role changes no live behavior: it bakes a bundle nothing selects, so it does not touch the #929 freeze surface.

Cross-reference: #1062 (filed earlier today by the exec seat) records Kai's librarian idea as a framing decision for the existing Echo lane, with the wording owned by the creator seat and gated on the Sirens admins and the identity eval. This issue is the complementary half: a distinct librarian roster role for a possible fourth lane, baked from the community person package. The two can land independently - #1062 needs no new role, and this role composes no lane until deployment picks one up. If #1062 resolves as 'name Echo the librarian', the fourth-lane build here may become unnecessary and this issue can close with that reason. The PR adding the role changes no live behavior: it bakes a bundle nothing selects, so it does not touch the #929 freeze surface.
Author
Member

Charter update on the PR branch (23d0d80): lookup-first is now doctrine, so when this lane's eval coverage gets built, it should carry a case checking that a reply opens from a retrieval rather than recall - the boundary-shaped version of what #1046 proposes for probes, and the enforceable half of the prose.

Charter update on the PR branch (23d0d80): lookup-first is now doctrine, so when this lane's eval coverage gets built, it should carry a case checking that a reply opens from a retrieval rather than recall - the boundary-shaped version of what #1046 proposes for probes, and the enforceable half of the prose.
Author
Member

Subsumed by coilysiren/inbox#382, the cross-repo aggregate. Closing as a tracker, not as a decision.

The fourth lane is now one of two branches in the epic's decision fork rather than a second open issue racing #1062. The option survives. If Kai picks the fourth lane, this reopens or the epic spawns the build issue.

Recorded in the epic: the role bakes from the community person package and verifies, nothing composes it, the seat ships as Libby (they) at placeholder quality, and the remaining work is a lane definition with its own Discord application, the deployment handover, eval coverage for the librarian charter, and a seat-naming review.

Exec read, non-binding: take the role onto Echo and drop the fourth lane. A fourth Discord application and identity to resolve a naming gap on an existing lane is a lot of surface, and coilyco-bridge/deploy#718 is live evidence that spare lanes cost more than they look like they cost. That is a recommendation and not the decision.

The lookup-first doctrine noted here is preserved as an eval line item in the epic.

**Subsumed by `coilysiren/inbox#382`**, the cross-repo aggregate. Closing as a tracker, **not as a decision.** The fourth lane is now one of two branches in the epic's decision fork rather than a second open issue racing #1062. **The option survives. If Kai picks the fourth lane, this reopens or the epic spawns the build issue.** Recorded in the epic: the role bakes from the community person package and verifies, nothing composes it, the seat ships as `Libby (they)` at placeholder quality, and the remaining work is a lane definition with its own Discord application, the deployment handover, eval coverage for the librarian charter, and a seat-naming review. **Exec read, non-binding: take the role onto Echo and drop the fourth lane.** A fourth Discord application and identity to resolve a naming gap on an existing lane is a lot of surface, and `coilyco-bridge/deploy#718` is live evidence that spare lanes cost more than they look like they cost. That is a recommendation and not the decision. The lookup-first doctrine noted here is preserved as an eval line item in the epic.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo#1063
No description provided.