Dashboard

Dashboard

An overview of what your agents have been doing.

Documentation
Active
12 pending review
Standup
Needs attention
3 missing today
Ticketing
Active
5 suggestions ready
Sprint Planner
Active
Sprint 24 — 6 days left
Release Coordinator
Active
v2.4 ships Thursday

Recent signals

Payments API now requires idempotency keys — docs updated
Documentation2h ago
Q3 planning sync — 3 decisions detected
Documentation5h ago
Deleting a shared attachment doesn't notify collaborators — flagged as a gap
Documentation1d ago
Sprint 23 wrapped — retro notes summarized
Standup1d ago

Last run

Completed 2 hours ago

4 PRs processed · 1 transcript ingested · 8 sections generated · 3 gaps flagged.

Next scheduled run in 4 hours.

Documentation
91% documentation coverage

8 sections across 3 features have gaps.

Documentation
3 features undocumented

Attachments, Videos, and Goals have no pages yet.

Standup
Avg standup response: 82%

3 team members consistently missing.

Documentation
PR velocity up 40%

Documentation may be falling behind code changes.

Documentation Agent Review queue

Review queue

12 drafts awaiting review before they publish to Notion.

Pending review
12+3 today
Approved this week
34+18%
Avg review time
4m 12s−42s
Auto-published
8this week
AI draft Medium confidence Generated 8m ago
AttachmentsFeature page
PR #83 · student-attachments Engineering / Features / Attachments

Overview

ApprovedUndo

Students can attach supporting files — most commonly PDFs — to a submission directly from the assignment view. Uploads are scanned, stored against the student's record, and surfaced to reviewers alongside the rest of the submission. Each file is capped at 25 MB and retained for the lifetime of the enrollment.

PR #83
Show context

API reference

Transcript · Jun 24

Upload an attachment for a given submission. The request must be sent as multipart/form-data.

POST /v1/submissions/{id}/attachments
fileThe binary file to upload. PDF, PNG, or JPG. Required.
visibilityEither private or shared. Defaults to private.
Show context

Edge case log

Best effort — no source
Generated without a source signal — no ticket or transcript context was found for this section. Review carefully before approving.

When an attachment is deleted, references to it are not removed outright — video previews that embedded the file fall back to a placeholder thumbnail, and goal entries drop it from their evidence list without notifying the goal owner. Shared attachments follow the same pattern: any collaborator with access loses it silently on their next page load rather than being notified in real time. There is currently no confirmation step before a shared attachment is removed for all parties.

Show context
Changes PR #1290 Updated 2h ago
Payments API — Idempotency Keys
Triggered by PR #1290 merged Jun 25 · Varshitha Daggolu
Sources used · PR #1290 · payments-svc transcript · Jun 25
Current
Proposed
Overview— no changes

Idempotency keys let clients safely retry payment requests without creating duplicate charges. A key is supplied per request and cached server-side for 24 hours.

Idempotency keys let clients safely retry payment requests without creating duplicate charges. A key is supplied per request and cached server-side for 24 hours.

API reference2 changes

The Idempotency-Key header is optional. Keys are retained for 24 hours before expiring.

Removed

The Idempotency-Key header is required for all POST requests. Keys are retained for 48 hours before expiring.

Added
Show context
Error codesNew section
—

A duplicate request with a reused key returns the original response with status:

409Key reused with a different payload.
422Key format invalid or too long.
Added
Show context

Published to Notion

2 sections published successfully.

View in Notion →

Returning to queue in 3 seconds...