v0.8.1 — 2026-11-10¶
The Questions Framework developer API can now copy a brain's Questions to another brain on its own: whole rubrics, the brain's slot types, the caller's own ids and every field of a Question.
Added¶
- Save a whole rubric over an Answer Key's draft (DEE-422).
PUT /v1/brains/{id}/answer-keys/{answer_key_id}/drafttakes the rubric asGET /questions/{question_id}returns it to a Curator: criteria, verdicts,gold,gold_whenand penalties. It returnsvalidation, which says why approval would refuse the draft yet. It needs a Curator or Admin key withquestions:write. Over MCP:save_answer_key_draft. - The brain's own slot types over the API (DEE-422).
POST /slot-typesproposes one (questions:write).POST /slot-types/{name}/approveapproves it with a Curator or Admin key (slots:write), and never the proposer's own.GET /slot-types?include_proposed=truelists the proposed ones too. Over MCP:propose_slot_type,approve_slot_type. - Your own ids (DEE-422). A proposal takes
question_id, and an Answer Key draft takesanswer_key_id. A taken id is409 conflict. - Every field of a Question on a proposal (DEE-422).
required_provisions,answer_shape, and whole slots ({name, type, required, ask_text, default}), not onlyname:type. - Tenant tooling.
scripts/qf_migrate_tenant.pycopies a store's Questions to a tenant through the developer API and verifies the result.devops/cdk/polaris-tenant/scripts/tenant_keys.pymints API keys on a tenant over SSM without the token appearing in any log.
See the API reference.
Upgrade notes¶
- No migration and no new configuration. The new routes sit behind the existing
qf_developer_apiandquestion_store_dbflags.