ai-inbox-conventions-hardening #16

Closed
opened 2026-05-09 23:25:37 +02:00 by codex · 0 comments
Collaborator

Parent: #2
Wave: 3 - Operations Hardening

Summary

Make AI Inbox conventions explicit and reusable so tools do not rely on ad hoc column names or fragile defaults.

Scope

  • Centralize AI Inbox board/column constants: Captured, Clarify, Ready, Doing, Waiting, Done / Archived.
  • Validate metadata shape: source, sourceRef, createdByKind, sensitivity, relationshipRef, projectRef, lastAiSummary.
  • Ensure AI-created cards get visible marker/comment/audit context.
  • Keep ensure_ai_inbox and AI Inbox convenience MCP tools first-class.

Non-goals

  • No Fastmail/Signal/Obsidian import pipelines yet.
  • No second-brain memory model.
  • No autonomous task grooming.

Acceptance Criteria

  • AI Inbox setup is deterministic from a clean workspace.
  • Metadata validation rejects invalid source/sensitivity values cleanly.
  • Iskra can create/move cards by column name without knowing workspace/list IDs.
  • AI-origin markers are visible enough to reconstruct why a card exists.

Tests / Smoke

  • MCP smoke: get_default_context -> ensure_ai_inbox -> create -> move -> activity.
  • Validation tests for metadata enums.
  • Regression for idempotent ensure_ai_inbox.

Rollback

Disable strict metadata validation behind compatibility mode if existing production cards are affected.

Owner Gates

Owner approval before changing production AI Inbox seed behavior.

Parent: #2 Wave: 3 - Operations Hardening ## Summary Make AI Inbox conventions explicit and reusable so tools do not rely on ad hoc column names or fragile defaults. ## Scope - Centralize AI Inbox board/column constants: Captured, Clarify, Ready, Doing, Waiting, Done / Archived. - Validate metadata shape: source, sourceRef, createdByKind, sensitivity, relationshipRef, projectRef, lastAiSummary. - Ensure AI-created cards get visible marker/comment/audit context. - Keep `ensure_ai_inbox` and AI Inbox convenience MCP tools first-class. ## Non-goals - No Fastmail/Signal/Obsidian import pipelines yet. - No second-brain memory model. - No autonomous task grooming. ## Acceptance Criteria - AI Inbox setup is deterministic from a clean workspace. - Metadata validation rejects invalid source/sensitivity values cleanly. - Iskra can create/move cards by column name without knowing workspace/list IDs. - AI-origin markers are visible enough to reconstruct why a card exists. ## Tests / Smoke - MCP smoke: get_default_context -> ensure_ai_inbox -> create -> move -> activity. - Validation tests for metadata enums. - Regression for idempotent `ensure_ai_inbox`. ## Rollback Disable strict metadata validation behind compatibility mode if existing production cards are affected. ## Owner Gates Owner approval before changing production AI Inbox seed behavior.
Sign in to join this conversation.
No labels
3plus3-followup
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
analytics
api
cockpit
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
docs
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
gemini-flash
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
leviathan
mcp
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
ops
priority:p0
priority:p1
priority:p2
priority:p3
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
safety
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
scout
security
size/large
size/medium
size/small
size/tiny
size/unknown
small-task
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tests
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
ui
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
pdurlej/kan-ductor#16
No description provided.