Rhythm 2.0 Specifications

Appearance

SVC-PFM-LLM-llmLLM foundation and AI usage

Markdown

SVC-PFM-LLM-llm

LLM foundation and AI usage

Markdown
  • DocumentDraft
  • ImplementationObserved

KindService contractProduct areaPlatformModuleAI Requests, Usage and the Jazz AI TeammateRevision1

Read atservices-platform ad3f6a65react-console baf6dae3

LLM foundation and AI usage ​

What This Service Is For ​

The LLM foundation executes declared model operations and accounts for their usage. It gives HQ staff historical and diagnostic reads, privileged controls and narrow evidence access, while customer administrators receive their own credit summary. Query generation uses this execution boundary; prototype general Jazz AI replies do not.

Boundary ​

The service owns request and task bookkeeping, operation and price history, allowance records, captured bodies and daily aggregates. Consuming features determine questions and validate answers. Security, Queries, email transport and workspace orchestration retain their respective delegated work. Prototype conversation storage remains in the console.

Operations in Words ​

Staff reads cover cross-organization history and one organization’s periods, requests, tasks, configuration and audit. Sensitive management operations preview or change limits, grant or revoke capacity and record corrections. Evidence access uses separate permission and eligible grants. Customer reads provide credits and feature availability. Internal functions execute tasks, publish declarations and perform maintenance.

Events and Jobs ​

No business-event producer or consumer is declared. The hourly worker recovers stale work, checks task totals, retries notices and refreshes daily reporting. Deployment publishes configuration, and workspace lifecycle invokes the purge participant. Metrics and alarms provide operational signals. No operation declares a Submissions binding.

Consistency Guarantees ​

Admission and control-audit transactions have explicit database boundaries. Request settlement and period movement do not share an automatic transaction, so interrupted accounting remains a finding. Notice handling and daily reporting complete later and can remain incomplete. Catalogue validation prevents invalid declarations from publishing, while separate appends can leave partial publication.

Owns
DOM-PFM-LLM-001DOM-PFM-LLM-002DOM-PFM-LLM-003DOM-PFM-LLM-004
Repository
services-platform

Controls

64 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-005 TC-AZ-006 TC-CHG-001 TC-CHG-002 TC-CHG-003 TC-CHG-004 TC-CHG-005 TC-CHG-006 TC-CHG-007 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-DAT-006 TC-IAM-001 TC-IAM-002 TC-IAM-003 TC-IAM-004 TC-IAM-005 TC-IAM-006 TC-LOG-001 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-MON-003 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-TEN-004 TC-VEN-001 TC-VEN-002 TC-VEN-003

Does Not Own

  • Consuming features construct the model question, validate its answer and decide domain effects.
  • Security owns staff authority, access grants, role audiences and security-audit storage.
  • Security and workspace lifecycle retain organization identity, status and calendar context.
  • Queries owns its execution engine, datasets and reusable reporting recipes.
  • Shared email transport and future notification delivery retain their separate owners.
  • Workspace lifecycle orchestrates deletion and invokes this module’s scoped participant.
  • Console conversation routes retain prototype Jazz AI projects and history.

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