Rhythm 2.0 Specifications

Appearance

WF-PFM-QRY-004Draft a query from a written request

Markdown

WF-PFM-QRY-004

Draft a query from a written request

Markdown
  • DocumentDraft
  • ImplementationObserved

Planning

Implements
CAP-PFM-QRY-003

KindWorkflowProduct areaPlatformModuleQuestions, record exploration and data deliveryRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

Draft a query from a written request ​

What It Does ​

A permitted person submits a written query request, optionally with an open query or settled predecessor for refinement. Clarification and unsupported responses are successful conversation outcomes without an executable draft.

The Flow ​

Validate the trimmed request, resolve the base dataset for the caller and check any supplied current query. Check the advisory allowance against the operation reservation estimate. Commit a working generation, then asynchronously invoke its worker with the workspace and generation identity. Rebuild the requester context and assemble permitted metadata and fenced request context. Keep the base and nearest whole datasets within the dictionary budget. Call the foundation with validation, bounded test-run and final-outcome tools, within the declared turn, tool, repair and time budgets. Apply deterministic defaults, validate the request and generation restrictions, and compile as the requester. Store an accepted query, clarification or unsupported outcome, or reject the final output. Poll the outcome and load an accepted draft into the designer for inspection and ordinary user-triggered execution.

When Something Fails ​

Refuse malformed input or missing access before admission. No generation row is created by these refusals. Refuse insufficient allowance with the foundation code and credit information. No generation is admitted by this allowance refusal. An observed invocation failure immediately settles the generation as failed. A crash after commit but before invocation can leave working status until reconciliation. Fail if the base context cannot fit or required configuration is unavailable. The request settles with a code rather than a partial dictionary submission. Provider or foundation failures return declared codes; invocation settlement accounts for actual spend. A process interruption may require foundation reconciliation of the reservation. Conditional settlement records a failure code; diagnostics stay in logs. Only one outcome is retained, including any permitted model-authored explanatory content. Translate the stored code into the console failure message. The person can still build a query manually after generation failure.

Idempotency and Concurrency ​

Each submission creates a generation and can incur another metered invocation. Conditional working-status settlement prevents two stored verdicts, but does not prove that a duplicate invocation performs no inference. Worker concurrency bounds environment processing. Foundation reservations and in-flight limits provide the spending and simultaneous-call gates; a working predecessor cannot be refined.

Controls

46 controls apply, from the corpus control catalogue.

TC-AI-001 TC-AI-002 TC-AI-003 TC-AI-004 TC-AI-005 TC-AI-006 TC-AI-007 TC-AVL-001 TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-006 TC-IAM-001 TC-IAM-002 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-SEC-001 TC-SEC-002 TC-SEC-003 TC-SEC-004 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

The Markdown files under specs/ in rhythmsoftware/rhythm-v2-docs are the canonical source of truth. This reader is a generated, read-only projection of them.

Rhythm Software