Spokbot — Build Status

Every unit of work in Spokbot is a user story with acceptance criteria, built BDD-first, then TDD. This page is generated from the repository's own story registry (tests/fixtures/user-stories.fixture.json) scored by the repository's own lints (storyLint + linkageLint) — the same checks the automated suites enforce. Nothing here is typed by hand; regenerate with node site/build-status.mjs.

26
stories in the registry
24
with BDD + TDD evidence
0
BDD only
2
no tests linked
0
dangling references
166/166
test files linked to stories
24/24
feature files linked to stories
0
lint errors

Stories

IDStoryPointsStatusAcceptance criteriaTest evidence
US-101As the engine, I want every tool execution to issue a structured receipt, so that completion decisions never depend on an agent's prose8in-progress3BDD + TDD
US-102As the CEO agent, I want to query what an agent actually did on a task, so that my standup reports effects, not claims3in-progress1BDD + TDD
US-103As Jesse (investor), I want a task to be markable done only when its postconditions verify against the real world, so that 'done' on my board always means the work observably happened8in-progress3BDD + TDD
US-104As a working agent, I want the engine to tell me mechanically which postcondition failed, so that my next attempt fixes the actual gap instead of re-reading my own prose3in-progress1BDD + TDD
US-105As the engine, I want contracted tasks to accept only schema-valid deliverables, so that tool-call syntax or narration in the final text is a failed attempt by construction5in-progress2BDD + TDD
US-106As a working agent, I want a wrong argument name to come back as a machine-readable correction, so that I can fix the call mechanically on the next round5in-progress2BDD + TDD
US-107As the CEO agent, I want mechanical task shapes to run as code, so that fetching, checking, and filing happen identically every cycle with no model in the loop8in-progress2BDD + TDD
US-108As Jesse (investor), I want every demo relayed to me to be backed by a receipt whose artifact still verifies, so that a link I click is a thing the engine itself made and just re-checked5in-progress2BDD + TDD
US-109As the CEO agent, I want tool-usage telemetry computed from the receipts ledger, so that standup numbers describe recorded events rather than regex inferences3in-progress1BDD + TDD
US-110As a business owner, I want the weekly content batch produced by the MACF team on the team's own schedule, so that Monday's drafts are the team's work and blockers surface the same day5in-progress4BDD + TDD
US-111As Jesse (investor/chairman), I want the MACF team to submit job applications itself through its own browser execution seat, so that submissions do not depend on the CEO's personal browser.13in-progress2BDD + TDD
US-112As Jesse, I want the applications ledger to be append-only, so that recorded submissions can never be lost or silently reverted to an earlier stage.8in-progress2BDD + TDD
US-113As Jesse, I want approved social content to publish as live posts, so that content work produces visible outcomes and not only drafts.8in-progress2BDD + TDD
US-114As Jesse, I want SEO recommendations turned into changed pages on staynalive.com, so that SEO counts as action, not just knowledge.8in-progress1BDD + TDD
US-115As Jesse, I want client deliverables counted only when actually sent, so that drafts are never reported as deliveries.3in-progress1BDD + TDD
US-116As the CEO, I want every MCP baseline server verified daily in the engine's own runtime context, so that a server cannot be fixed in one context and broken in the one the team uses.8in-progress1BDD + TDD
US-117As the CEO, I want the directive dead-letter store inspected daily, so that no directive dies silently.5in-progress1BDD + TDD
US-118As Jesse, I want every recurring team function to exist as a story in the planning system before it runs, so that no work is invisible to the team or to me.5in-progress1BDD + TDD
US-119As Jesse, I want the CFO to run a daily finance snapshot and land every newly discovered expense in my budget sheet in the same pass, so that revenue operations reflect real money movement, not plans.5in-progress1BDD + TDD
US-120As Jesse, I want AI audit outreach batches sent on schedule with replies watched continuously and follow-ups drafted for my one-click review, so that the 50 AI Readiness Audit pipeline produces conversations, not silence.5in-progress1No tests linked
US-121As Jesse, I want my Facebook, Instagram, LinkedIn, and Threads messages watched and real messages triaged with drafts in my voice for my approval, so that no genuine message waits unanswered and nothing sends without my go-ahead.5in-progress1No tests linked
US-122As Jesse, I want every agent to produce visible demos that are relayed to me after the agent demos to the CEO, so that silence from any agent is treated as breakage, not as a quiet week.3in-progress1BDD + TDD
US-123As Jesse, I want the engine, Vikunja, gateway, and n8n kept up by a watchdog that auto-restores known failure classes, so that health means workflows actually execute, not that a heartbeat is fresh.8in-progress1BDD + TDD
US-FW-018As a Spokbot operator, I want Vikunja supervised by a watchdog that restarts it with setsid and never kills itself, so that the team's board survives session teardown and never dies silently3in-progress4BDD + TDD
US-FW-025As a Spokbot operator, I want the autonomous driver verifiably scheduled, so that a working driver script with no schedule is detected as a critical defect instead of agents going silent3in-progress3BDD + TDD
US-FW-031As the CEO of the Spokbot team, I want requirements broken down into assigned user stories by the PM, so that a content or visual requirement becomes platform-sized stories with acceptance criteria on the board instead of one vague ask3in-progress3BDD + TDD