mosaicstack/stack
25
0
Fork 1
Code Issues 344 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

Row 6 code phase: record and display task-setter attribution #1511

New Issue
Open
opened 2026-09-14 14:06:37 +00:00 by darkwing · 0 comments
darkwing commented 2026-09-14 14:06:37 +00:00
Member
Copy Link
Copy Source

Task attribution, row 6 code phase

Jason accepted row 18 and has explicitly required automatic continuation after
accepted iterations. This starts the next already-briefed item, row 6 of QUEUE,
under the existing control-board MVP plan's Piece 5. The newer standing start
instruction replaces that piece's historical Sunday start-message scheduling;
its ordering and protected-action gates remain. Use repository-native agents,
not fleet launchers. Rows 9-13 still wait for row 6 completion.

Source assignment

Rocko implements the code phase from the internal agents/rocko profile in the
canonical checkout, refactor. Filbert independently reviews backend/schema/tests;
Dewey independently reviews presentation. Darkwing coordinates and owns tracking.
The existing Rocko native process uses the older tmux socket; this is not a
managed fleet worker assignment or authority to change its launcher.

Implement the already-approved taskSetBy requirement: mosaic seat task records
an explicit --by NAME, otherwise MOSAIC_AGENT_NAME, otherwise unknown. Board
serialization and both current board presentations display it by the task source.
This is caller-supplied attribution, never authenticated identity or authorization.

Scope: packages/seat source/tests/docs, packages/control-board source/tests/docs,
and minimal WebUI presentation/tests. Preserve existing attention and Discord-row
changes exactly except the necessary additive integration. No launcher, connector,
role, credential, home, live registration or service changes; no commits/push by
the author. Use isolated fixtures, not actual seat task mutation during development.

Acceptance:

  • Explicit --by wins over environment; absent/empty environment gives unknown.
    Invalid explicit input refuses before writing. Values are bounded and escaped.
  • Existing registration records without taskSetBy still load, showing unknown.
    No breaking registration version change or implicit migration of old files.
  • Preserve unrelated registration fields and original startedAt on task updates.
  • Display attribution only for the task actually selected: no stale registration
    attribution on a transcript-derived task, and no borrowing native attribution
    for a Discord connector's fixed task. Attribution never enables replies/access.
  • Isolated CLI/schema/scanner/browser regressions, exact frozen handoff and
    independent review. Existing accepted behavior remains covered.

This code phase precedes the plan's specified first Filbert behavior assignment,
Relaunched seat shows the old last message. Do not start that concurrently.
Gate F and its human-message evidence are not claimed by this code phase; record
actual future dates, not the old plan's anticipated 2026-09-13 measurement.
No live backend replacement or publication follows automatically from source tests.

# Task attribution, row 6 code phase Jason accepted row 18 and has explicitly required automatic continuation after accepted iterations. This starts the next already-briefed item, row 6 of QUEUE, under the existing control-board MVP plan's Piece 5. The newer standing start instruction replaces that piece's historical Sunday start-message scheduling; its ordering and protected-action gates remain. Use repository-native agents, not fleet launchers. Rows 9-13 still wait for row 6 completion. ## Source assignment Rocko implements the code phase from the internal agents/rocko profile in the canonical checkout, refactor. Filbert independently reviews backend/schema/tests; Dewey independently reviews presentation. Darkwing coordinates and owns tracking. The existing Rocko native process uses the older tmux socket; this is not a managed fleet worker assignment or authority to change its launcher. Implement the already-approved taskSetBy requirement: mosaic seat task records an explicit --by NAME, otherwise MOSAIC_AGENT_NAME, otherwise unknown. Board serialization and both current board presentations display it by the task source. This is caller-supplied attribution, never authenticated identity or authorization. Scope: packages/seat source/tests/docs, packages/control-board source/tests/docs, and minimal WebUI presentation/tests. Preserve existing attention and Discord-row changes exactly except the necessary additive integration. No launcher, connector, role, credential, home, live registration or service changes; no commits/push by the author. Use isolated fixtures, not actual seat task mutation during development. Acceptance: - Explicit --by wins over environment; absent/empty environment gives unknown. Invalid explicit input refuses before writing. Values are bounded and escaped. - Existing registration records without taskSetBy still load, showing unknown. No breaking registration version change or implicit migration of old files. - Preserve unrelated registration fields and original startedAt on task updates. - Display attribution only for the task actually selected: no stale registration attribution on a transcript-derived task, and no borrowing native attribution for a Discord connector's fixed task. Attribution never enables replies/access. - Isolated CLI/schema/scanner/browser regressions, exact frozen handoff and independent review. Existing accepted behavior remains covered. This code phase precedes the plan's specified first Filbert behavior assignment, Relaunched seat shows the old last message. Do not start that concurrently. Gate F and its human-message evidence are not claimed by this code phase; record actual future dates, not the old plan's anticipated 2026-09-13 measurement. No live backend replacement or publication follows automatically from source tests.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-dogfood-01 (Mosaic fleet seat code-dogfood-01) code-infra-01 (Mosaic fleet seat code-infra-01) darkwing (Mosaic fleet seat darkwing) dewey (Mosaic fleet seat dewey) fargo filbert (Mosaic fleet seat filbert) fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) marcie merge-gate ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) orch-01 (Mosaic fleet seat orch-01) pepper resume rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) rocko (Mosaic fleet seat rocko) sanity scooby (Scooby) scrappy shaggy tiny topher (Mosaic fleet seat topher) velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1511