hub/tasks/architecture/storage/define-sync-field-split.md at main

alkdev/hub

Files

glm-5.1 2b63cda1c7 Setup repo: migrate architecture specs, code stubs, and tasks from alkhub_ts

Copy architecture docs, ADRs, storage domain specs, research, reviews,
and 56 storage architecture tasks from the alkhub_ts monorepo. Adapt for
standalone @alkdev/hub repo structure (src/ not packages/hub/).

Sanitize all sensitive information:
- Replace private IPs (10.0.0.1) with localhost defaults
- Remove internal server hostnames (dev1, ns528096)
- Replace /workspace/ private paths with npm package references
- Remove hardcoded credentials from examples
- Rewrite infrastructure.md without private network details

Add Deno project scaffolding: deno.json (pinned deps), .gitignore,
AGENTS.md, entry point. Migrate existing code stubs (crypto, config
types, logger) with updated import paths.

2026-05-25 10:56:32 +00:00

1.7 KiB

Raw Permalink Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

define-sync-field-split

Define sync vs runtime field split for tasks

completed

narrow

high

phase

implementation

Description

The task sync does a full upsert, but the Authority Model says runtime status mutations go through hub.task.updateStatus. If sync blindly writes frontmatter status, it can clobber runtime state. Example: Agent sets task.status = 'in-progress' via hub operation, then decomposer edits the task file (still has status: pending), then sync runs and overwrites in-progress back to pending.

Define the sync field split explicitly in tasks.md: sync upserts authored fields (slug, name, path, scope, risk, impact, level, priority, tags, assignee, due, body, fileCreatedAt, fileModifiedAt, depends_on) and must not overwrite runtime-managed fields (status, startedAt, completedAt). Runtime fields are only mutated via hub.task.* operations.

Acceptance Criteria

tasks.md has an explicit "Field Authority Split" section listing authored fields vs runtime-managed fields
The sync flow specification is updated: upsert uses ON CONFLICT DO UPDATE SET only for authored fields
Runtime fields (status, startedAt, completedAt) are explicitly excluded from the sync upsert
The Authority Model table in tasks.md is updated to include the field-level split
A warning is added: "Sync must never write status, startedAt, or completedAt — these are owned by hub operations"

References

docs/reviews/storage-architecture-review-2026-04-21.md#C07
docs/architecture/storage/tasks.md:296-325

Notes

To be filled by implementation agent

Summary

To be filled on completion

1.7 KiB Raw Permalink Blame History