cardmem.com

Showing 25 of 192 from the live probe.

• Cardmem Design Consult

  F280.10 — ASK THE DESIGN GUIDE before you build or change a surface, and get back WHERE it goes and HOW it should look: the sections of this project's DESIGN.md that bind this change, the token names to use instead of raw values, and the headings that exist but did NOT match. Answers from the guide's own words, never a paraphrase. Three distinct outcomes you must tell apart: `covered` (the guide has rules for this — follow them), `silent` (the guide exists and says NOTHING about this — you are c

• Cardmem Promote Mockup To Design

  F280.11 — after a mockup is APPROVED, see what it DECIDED that the project's DESIGN.md does not yet have. Returns a PROPOSAL in three groups: `already` (a count of values that are existing tokens — the mockup obeying the guide), `near` (close to a token, reported WITH the distance and never auto-mapped, because only a human knows whether a 4%-off value is a mistake or a deliberate distinction), and `additions` (genuinely new — the actual decision). READ-ONLY BY CONSTRUCTION: there is no way for

• Cardmem List Projects

  List all projects in the current org. Returns id, slug, name, github_repo_full_name, board_count, and the F143 product definition (vision, mission, scope + the vision_filled predicate that gates vision-based agent features).

• Cardmem List Cards

  List cards in a project. Filters: board_id, column, kind (epic|story|task|subtask), parent_card_id (exact), has_parent (true=children only, false=roots only), assignee_id. Each card row carries plan_file_path: either its own plan-doc or, walking up the parent chain, the nearest ancestor that has one (so a story without its own plan inherits its epic's).

• Cardmem Get Card

  Get a card by id or global_slug (e.g. "projects-F001"). With include_tree=true, returns 1-level children and a 3-level subtree. Epics get a rollup with story-point and child-status aggregates. Archived cards return with archived=true flag — pass error_on_archived=true for the old hard-error behaviour.

• Cardmem Card By Plan Path

  F007.5 — Resolve the card linked to a plan-doc by its repo-relative file_path (plans.file_path → plans.card_id). Returns { card: { id, f_number, title, status_column } } or { card: null } when no card is linked. Robust over filename-F-number parsing — works for non-F-numbered docs (e.g. init.md).

• Cardmem Relink Plan

  F288.23 — Point a card at a plan-doc that ALREADY EXISTS, without re-sending its body. Use when docs are consolidated or renamed and a card's plan-link now names a file that is gone: the review gate then reads a document that does not exist and reports findings about it that are not true. The target plan MUST already be known to cardmem — this moves a pointer, it never creates a plan, so it cannot be used to point a card at a document nobody has written. The previously linked plan is NOT deleted

• Cardmem Suggest Next F Number

  Suggest the next free F-number. Without parent_card_id: next top-level integer (F001, F002, …). With parent_card_id: next sub-segment under that parent (F09 → F09.3 if F09.1 + F09.2 exist). Returns suggested, latest, gaps — and `reserved: false`, because THIS IS A READING, NOT A CLAIM: nothing marks the number taken, so a card created seconds later can lose the race. It now also scans the project PLAN-DOC paths, not only the board, since a plan-doc committed before its card exists is exactly the

• Cardmem List Md Files

  List markdown files registered in the project: plan-docs (plans table) + research docs (research_docs table, docs/research/). Full repo scan = F003 GitHub App.

• Cardmem Read Md

  Read a markdown file from a project: a plan-doc (plans/plan_drafts) OR a research doc (research_docs, docs/research/). Returns { content, commit_sha, last_modified, source }.

• Cardmem List Skills

  List skills registered in a project (entries from /skills/).

• Cardmem List Agents

  List agents registered in a project (entries from /agents/).

• Cardmem List Mcps

  List MCP entries registered in a project (entries from .mcp.json).

• Cardmem Scan Repo

  Scan a GitHub repo for cardmem-onboarding state: docs/features/F<n>.md plan-docs (always) and (when include_gaps=true, default) a gap-report listing missing canonical artifacts — CLAUDE.md "Project layout"/"Working with cardmem" sections, .mcp.json cardmem entry, .claude/skills inventory, docs/features folder, ROADMAP.md, FEATURES.md. NEVER writes to the target repo. Optional project_id pre-checks which F-doc proposals would be duplicates of existing cards in that project.

• Cardmem Search

  Fuzzy search across cards (title, f_number, global_slug, role, task) and plan-docs (file_path + content). Returns mixed result list ordered by match quality (title-match > f_number-match > content-match). Pass project_id to scope; omit for org-wide. Pass exact:true for whole-word matching (e.g. "ROA" matches the token ROA but not "ROADMAP").

• Cardmem List Mcp Keys

  List API keys belonging to the current user. Returns name, first 6 chars of the hash, created_at, last_used_at, and revoked_at — never the plaintext. Use 'include_revoked: true' to see historic keys.

• Cardmem List Incident Keys

  List incident-ingest keys for a project. Returns name, hash prefix, created/last-used/revoked timestamps — never the plaintext. Pass include_revoked:true to see historic keys.

• Cardmem List Inbox Webhook Keys

  List Inbox Webhook keys for a project. Returns name, hash prefix, rate-limit, created/last-used/revoked timestamps — never the plaintext. Pass include_revoked:true to see historic keys.

• Cardmem List Dependencies

  List all dependency edges in a project. Returns {from_card_id, to_card_id, type} rows. Used by /roadmap to draw arrows within releases and (in F050) by the corpus graph to render the full topology.

• Cardmem Card Verdict

  F095.1/F095.11 — The aggregate Review→Done verdict for a card: latest status per check-type (code/security/lens/ac/design), the AC gate, ready_for_done (AC gate satisfied AND code+security passed AND any recorded lens/ac/design passed AND nothing blocking), blocked_by (F095.14 — when ready_for_done is false, one human-readable line per blocking condition naming what to do about it; [] when true. NOTE the case it exists for: all acceptance criteria can be ticked (ac_gate.satisfied true) while an

• Cardmem Review Debt

  F095.26 — what the Review→Done gate OWES, as a fact derived from the cards rather than a directive that was sent once. Returns `counts` over EVERY non-archived card in Review (never_assessed = no acceptance criteria · unfinished = criteria not all met · awaiting_receipt = every criterion met and a required review was NEVER recorded, i.e. finished work waiting on a receipt · blocked_by_finding = every criterion met but a recorded check says no · ready = would pass the gate today), plus a list, ol

• Cardmem List Reports

  F095.8/F095.9 — List a project's reports (newest first), optionally filtered by type ('review' = Full-Auto-Review bundles; cost/incident/audit later). Backs the /reports route.

• Cardmem List Mockups

  F122 — List a project's mockups (newest first), optionally scoped to one source (idea/card) or status. Includes each mockup's current-version HTML by default (gallery thumbnails) — pass include_html:false for a lighter payload. Backs the Mockups gallery + the "Mockups (N)" cross-link section.

• Cardmem Get Mockup

  F122 — One mockup with ALL its versions (html + changelog, newest first), its notes thread, and a resolved back-link to the idea/epic/card that created it. Backs the mockup viewer + version timeline + visual diff. Pass include_html:false to refresh notes/metadata WITHOUT the (potentially multi-MB) version HTML — the versions come back with html:null and the heavy blob column is not read (F233.2, the note-refresh path).

• Cardmem List Mockup Shares

  F167.3 — The active share and its named recipients (invited / accepted) for a mockup. Does NOT tell you who can SEE the mockup: the customer portal lists by PROJECT scope, so a share with zero recipients is still readable by every accepted customer of that project. Nor does it tell you whether anyone has viewed it — there is no view tracking.