Cited to the line
Every claim links to a real file and line range. Footnotes, not paraphrase — the manager can open the source in one click.
Not a wiki to maintain — a living document Blockd compiles per ticket, grounded in your real code and cited to the line. Below is an actual generated brief, untouched.
Welcome to Blockd Onboard. Your first backlog entry point is BOT-11 — a UI-oriented, backend-adjacent task that makes audit data visible without relying on direct SQL access. You’ll work in KNQuoc/blockd-onboard, a private TypeScript repo on the main branch.
Keep two audit concepts separate. Access declarations write an AccessDeclarationAuditLog row on create, update and delete — queryable via listAuditLogs(companyId, projectName), ordered by time descending. Provision and revoke events write accessProvisionAuditLog rows; the revoke path writes a revoke_requested breadcrumb before any GitHub call.
Use .env.example as the checklist — DATABASE_URL, AUTH_SECRET, AUTH_GITHUB_ID, AUTH_GITHUB_SECRET, AUTH_URL and LINEAR_API_KEY. The compose service postgres runs pgvector/pgvector:pg16 on 5432:5432. That matters here because the viewer depends on rows persisted through the Prisma-backed access flows, not mocked client state.
Trace the existing audit presentation in AccessSettingsClient.tsx — the “Audit log” section renders declaration edits only: action, target, actor email, timestamp. Then trace the server-side provision/revoke audit data. A good first slice: extend that surface with provision/revoke entries using the same company and project scoping as listAuditLogs(companyId, projectName).
Embedded access bundle
BOT-11 needs exactly one scope: write access to the repo it changes. Routed to the declared owner; if approval blocks the first task, escalate through Repo admins.
The evidence package did not include a matched decision thread for BOT-11. Before you commit to table columns, filters, retention language, or who can see the viewer, confirm the desired behavior with your manager or the ticket owner. Use the code as the current contract — not as the product decision.
Prior-work search surfaced live code references rather than a reverted prior BOT-11 attempt. Start with AccessSettingsClient.tsx — it already contains an audit-log rendering pattern close to the requested viewer.
Why a manager signs off on this
Every claim links to a real file and line range. Footnotes, not paraphrase — the manager can open the source in one click.
Missing decision threads and setup blanks are flagged “needs manager input,” never hallucinated into confident prose.
Surfaces same-file history and previous attempts so the new hire builds on what exists instead of re-deriving it.
The bundle is derived from the ticket’s code paths and routed to the declared owner — not a separate ticket to chase.
Blockd turns any ticket into a cited brief and a one-click access bundle. Your institutional memory, mounted per hire.