AIMFP

Get the architectural flow IDs for a task. Use to understand which part of the codebase a task touches and find relevant files.

Get the tasks of a milestone (any status, or one status with status=...). Lean by default: descriptions null.

Advanced task search with multiple filters

Get theme by name (fairly frequent)

Get all themes for a flow

Get the themes a completion path advances (id, name, description).

Get tracking notes with optional filters

Get all tracking feature flags

Look up a tracked type by name with full definition and file location — use BEFORE reading source files. Returns definition_json and description.

Find files not assigned to any module. Useful for identifying tracking gaps — domain logic files that should belong to a module but haven't been assigned.

Get field names and types for a specific table in user_directives.db

Get available fields for table to use with generic add/update operations. Returns field names, types, and whether required.

Get complete schema SQL for user directives database

List all tables in user directives database

Get a single user directive by its unique name

Get notes from user_directives.db with optional filters. All filters are AND logic. No filters returns all notes.

Get project-wide user setting by key (fairly frequent)

Get all user settings from user_settings table (complements get_user_setting which gets one setting by key)

Get all directive flows from wildcard '*' source (available from ANY context). Includes FP references, utilities, cross-cutting concerns.

Initialize user_directives.db for Case 2 (custom directive automation) projects. Creates the database from schema. Call when project transitions to Case 2.

Link files to a task, subtask, or sidequest (task_files junction) so get_task_context and get_task_files return them. Files are linked automatically when reserved, finalized, cataloged, or updated (and when their functions/types are finalized, cataloged, or updated) while a work item is in_progress — the most recent in_progress sidequest, else subtask, else task. Use this for files worked on before the item was in_progress, or to correct a link.

List all AIMFP work branches from work_branches table

List available backup archives, newest first, with size, modification time, and which targets each one actually contains. Read-only. Call BEFORE restore_project_backup: a backup only holds databases that existed when it was taken, so an older archive may not carry every target you want.

Load all active preferences for a directive (high-frequency)

(For use with InterCommAIMFP) ONE-CALL branch-ref merge orchestrator: takes a branch name and runs the whole documented sequence internally — export_state_changeset, optional source text-merge (keeping main's project.db, never blob-merging it), then apply_state_changeset — returning only a small result/conflict summary. The ~8k-token changeset never crosses the agent boundary, so a real fan-out stops serializing on the master hand-carrying blobs. Idempotent like apply; records a merge_history row; conflicts are still returned as structured data (never guessed). Mutates the working project.db (after backup) and leaves the source merge uncommitted for you to review and commit.

(For use with InterCommAIMFP) Batch wrapper over merge_worker_branch: integrate a list of worker branches one at a time, each moving main forward and re-minting against the prior. 'additive-first' ordering lands the low-risk purely-additive branches before any structural/deleting ones. Each branch goes through the full export->source-merge->apply sequence; conflicts are surfaced per branch, never guessed.

Migrate all pending project databases to current schema versions, in place. Per database: refuses if another connection has it open, write-locks it, keeps a pre-migration copy at <project folder>/backups/<db>_pre_migration_v<old>_<YYYYMMDD>.db (never overwriting an earlier copy), rebuilds it from the new schema SQL (shared columns via ATTACH), verifies row counts and atomically swaps the rebuilt file in. A count mismatch or any error leaves the original untouched (placed=false, error). Nothing is left in temp folders.

Re-point many files from one flow to another in one transaction — the tool for splitting an oversized flow or retiring one. Moves links only; files are never touched. Files not in the source flow are skipped.

Re-point many flows from one theme to another in one transaction (e.g. when a theme is split or merged). Flows not in the source theme are skipped.

(For use with InterCommAIMFP) Compute DISJOINT file/module partitions so parallel workers don't overlap — the cheap complexity lever that converts most semantic conflicts into non-events. Only AIMFP can compute this well because it owns the function->function interaction graph and type-usage edges that define real dependency boundaries. Builds an undirected file-coupling graph (interaction edges + type-usage edges + module co-membership), takes connected components as atomic ownership units (never split), and bin-packs whole components into n_workers balanced partitions. Returns proposed per-worker ownership sets plus shared/contended files. Pure read; a planning aid you may tweak or override.

Returns list of allowed values for CHECK constraint enum fields in project.db. Parses schema to extract CHECK(field IN (...)) constraints.

Execute complex SQL WHERE clause (advanced, rare use)

Execute complex SQL WHERE clause (advanced, rare use)

Flexible SQL-like query interface for complex project queries. Provides powerful filtering and joining capabilities without writing raw SQL.

Execute complex SQL WHERE clause (advanced, rare use)

Execute complex SQL WHERE clause on user_directives.db (advanced, rare use)

Bring the tracking of changed files up to date in ONE call and one transaction (after a git pull, external edits, or edits made outside reserve/finalize). Per path: an untracked file is cataloged with its functions and types; a tracked file gets functions/types newly present in its source cataloged (existing rows and their prose are never touched) and those no longer in the source reported; a tracked file gone from disk is renamed as declared in renames, else to the one untracked path in the call with the same file name, else reported missing; a legacy row recorded at a folder path ('.' or a directory) is adopted by the one new file with its name instead of being duplicated (reported in files_renamed). Then adds the affected files' call edges (Python), skipping edges already tracked, and reports tracked call edges whose target the caller no longer references, directly or through the untracked same-file helpers it uses (stale_interactions). A tracked _private function is never reported missing just because include_private is false. Never deletes anything. Honours watchdog exclusions.

Remove a file-flow link from the file_flows junction table. Use when reassigning a file to a different flow or preparing for file deletion.

Remove a file from a module. Deletes module_files junction entry. File itself is not deleted.

Batch remove multiple files from modules. More efficient than multiple remove_file_from_module calls. Skips non-existent entries, reports modules left empty.

Batch-unlink flows from themes. A note is required. Refused (whole batch) if any flow would be left with no theme — link the replacement first, or use move_flows_to_theme.

Batch-unlink milestones from flows. A note is required. Refused (whole batch) while an open task or sidequest of that milestone still lists the flow in its flow_ids — update those first.

Batch-unlink completion paths from themes. A note is required.

Fix gaps and duplicates in order_index

Change order_index for a completion path

Reserve a file ID before writing code, declaring the flow(s) it implements — part of the mandatory reserve-write-finalize tracking flow. flow_ids is required: a list of flows, or an explicit null for a file with no flow. Returns ID to embed in filename.

Batch-reserve file IDs before writing code, each declaring the flow(s) it implements (flow_ids list, or explicit null for no flow). Atomic: all reserve or none.

Reserve a function ID before writing code. Include purpose, parameters, and returns — null fields make functions invisible to future sessions.

Batch-reserve function IDs before writing multiple functions. Include purpose/parameters/returns for every function.

Reserve a type ID before writing the definition. Include definition_json and description — null fields force full file reads in future sessions.