Decision Records

How Rhythm 2.0 is built. Each decision record (ADR) states the choice, the alternatives weighed against it, why it was selected, and what it rules out for the implementation that follows. None are authored yet: they belong to the design stage.

Decisions 574

ADR-ACC-BAT-001Resolve and retain accounting when the batch postsProposed
ADR-ACC-BAT-002Commit accounting atomically and report refused writesProposed
ADR-ACC-BAT-003Remove ordinary ledger generations while retaining posting historyProposed
ADR-ACC-BAT-004Use named lifecycle commands for ordinary batchesProposed
ADR-ACC-BAT-005Prepare scheduled posting before retirement commitsProposed
ADR-ACC-BAT-006Keep collection and ledger ownership in Batch ManagementProposed
ADR-ACC-BAT-007Declare no custom-field capability for Accounting batchesProposed
ADR-ACC-BAT-008Keep current batch operations unpublished to SubmissionsProposed
ADR-ACC-BAT-009Model intake configuration as Batch facetsProposed
ADR-ACC-BAT-010Enforce immutable balanced ledger rows in minor unitsProposed
ADR-ACC-BAT-011Distinguish optional-version patches from versioned replacementsProposed
ADR-ACC-BAT-012Gate posting attention on deployment readinessProposed
ADR-ACC-BAT-013Run generation in the accounting task functionProposed
ADR-ACC-BAT-014Record unresolved batch-versus-document accounting placementProposed
ADR-ACC-BKS-001Shared configuration with explicit writing responsibilitiesProposed
ADR-ACC-BKS-002Versioned replacements with explicit omission rulesProposed
ADR-ACC-BKS-003Fixed founding values with service and database protectionProposed
ADR-ACC-BKS-004Physical deletion with declared dependency protectionProposed
ADR-ACC-BKS-005No custom-field capability in the examined configurationProposed
ADR-ACC-BKS-006Explicit Submissions exclusions for configuration and maintenanceProposed
ADR-ACC-BKS-007Resolve accounting destinations when postingProposed
ADR-ACC-BKS-008Atomic configuration writes with provider calls before persistenceProposed
ADR-ACC-BKS-009Explicit fiscal generation with calendar checks at commitProposed
ADR-ACC-BKS-010Tax configuration remains a transitional Accounting responsibilityProposed
ADR-ACC-BKS-011Shared dispatch and run history for recurring workProposed
ADR-ACC-BKS-012Platform orchestrates Accounting lifecycle participantsProposed
ADR-ACC-BKS-013Shared template selection with producer adoption still incompleteProposed
ADR-ACC-BKS-014No configuration change stream or revision historyProposed
ADR-ACC-BKS-015Workspace row policies with explicit global vocabulariesProposed
ADR-ACC-CLS-001Close Controls Period Status on the Shared CalendarProposed
ADR-ACC-CLS-002Requests Persist Separately from Their Execution JobsProposed
ADR-ACC-CLS-003Execution Rechecks Readiness While Holding the Period LockProposed
ADR-ACC-CLS-004The Period Lock Coordinates Close Work with PostingProposed
ADR-ACC-CLS-005Command Replay Compares the Saved RequestProposed
ADR-ACC-CLS-006Finalization Stores Closure, Evidence and the Aging Request AtomicallyProposed
ADR-ACC-CLS-007Recovery Continues Committed Recognition Before ReversalProposed
ADR-ACC-CLS-008Calendar Maintenance Follows Successful ClosureProposed
ADR-ACC-CLS-009Snapshots and Job Events Supply the Closing EvidenceProposed
ADR-ACC-CLS-010No Custom-Field Inputs Appear in the Examined Close BoundaryProposed
ADR-ACC-CLS-011Close Operations Have No Submissions PublicationProposed
ADR-ACC-CLS-012Workspace Grants Authorize Close and Reopen ActionsProposed
ADR-ACC-CLS-013Execution Uses System Authority after Request AcceptanceProposed
ADR-ACC-CLS-014Deployment Currently Shares Accounting FunctionsProposed
ADR-ACC-PRD-001One Common Product Identity With Domain-Owned ExtensionsProposed
ADR-ACC-PRD-002Domain Transactions Include the Common Product WriteProposed
ADR-ACC-PRD-003Product Kind Ownership Restricts Service WritersProposed
ADR-ACC-PRD-004Financial Setup Has Independent Permissions and VersioningProposed
ADR-ACC-PRD-005Versions Detect Stale Writes; Product Locks Serialize Local ChangesProposed
ADR-ACC-PRD-006Replacement Omission Semantics Remain UnresolvedProposed
ADR-ACC-PRD-007Product Configuration Does Not Opt Into Custom FieldsProposed
ADR-ACC-PRD-008Owned Template Changes Cross the Product Transaction BoundaryProposed
ADR-ACC-PRD-009Purchase Consumers Apply Stored Selling ConfigurationProposed
ADR-ACC-PRD-010Posting Freezes Accounts Resolved From Current ConfigurationProposed
ADR-ACC-PRD-011Existing Product Tax Records Await the Commerce TransferProposed
ADR-ACC-PRD-012Creation Establishes a Permanent Readable Product IdentityProposed
ADR-ACC-PRD-013Shared Table Reads and Durable Migration HandoversProposed
ADR-ACC-PRD-014Submissions Publication Is Not Established by These SourcesProposed
ADR-ACC-PRD-015History and Change Events Remain an Open Product ChoiceProposed
ADR-ACC-REC-001Reconciliation Is a Module of the Accounting ServiceProposed
ADR-ACC-REC-002Settlement Items Are Written in the Causing TransactionProposed
ADR-ACC-REC-003Outstanding Standing Is Derived for the Requested DayProposed
ADR-ACC-REC-004Money Has One Active Holder, Decided by the DatabaseProposed
ADR-ACC-REC-005Finalized Reconciliations Are Reversed and Redone, Never ReopenedProposed
ADR-ACC-REC-006A Second Person Finalizes by Default, with an Audited WaiverProposed
ADR-ACC-REC-007Ledger Requests Ride in Operational Batches; Reconciliation Never PostsProposed
ADR-ACC-REC-008The Merchant Account's Ledger Account Is the Processor Clearing AccountProposed
ADR-ACC-REC-009Readiness Is Assessed Inside the Close Transaction, One Finding per ProblemProposed
ADR-ACC-REC-010Accepting a Blocker Takes Two PeopleProposed
ADR-ACC-REC-011Reconciliation Keeps Its Own Append-Only Audit TrailProposed
ADR-ACC-REC-012Money Commands Take Request KeysProposed
ADR-ACC-REC-013Reconciliation Records Carry No Custom FieldsProposed
ADR-ACC-REC-014No Reconciliation Operation Is Published to SubmissionsProposed
ADR-ACC-REC-015Permissions Are Workspace-Wide in the First ReleaseProposed
ADR-ACC-REC-016Payouts Are Entered by Hand; Processor Import Comes LaterProposed
ADR-ACC-REC-017Daily Checks Run on Accounting Schedules per WorkspaceProposed
ADR-ACC-REC-018Refusals Carry Stable Codes and Lifecycle Refusals Are AuditedProposed
ADR-ACC-REC-019Money Is Integer Minor Units; Ledger Requests Are Two-Decimal for NowProposed
ADR-ACC-REC-020Drafts Change by Versioned Commands; Payout Correction Replaces the Whole RecordProposed
ADR-ACC-TRX-001Billing Ownership and Posting ResponsibilityProposed
ADR-ACC-TRX-002Database Maintenance of Ledger BalancesProposed
ADR-ACC-TRX-003Versioned Preparation and Explicit Issued CorrectionsProposed
ADR-ACC-TRX-004Retained Financial Reversals and Unposted AmendmentProposed
ADR-ACC-TRX-005Committed Attempts Around External Payment CallsProposed
ADR-ACC-TRX-006Scoped Financial Retries and Communication DeduplicationProposed
ADR-ACC-TRX-007No Custom Fields on Financial RecordsProposed
ADR-ACC-TRX-008Separate Commerce Service Capability GrantsProposed
ADR-ACC-TRX-009Cutoff-Aware Receivable Facts and AgingProposed
ADR-ACC-TRX-010Acknowledgement Before Commerce Receiver ConfigurationProposed
ADR-ACC-TRX-011Receipt Money and Independent Credit ApplicationsProposed
ADR-ACC-TRX-012Allocation Release During Billing ReductionProposed
ADR-ACC-TRX-013Commerce Tax Ownership With a Staff-Billing GapProposed
ADR-ACC-TRX-014Unpublished Transaction Intake ContractsProposed
ADR-ACC-TRX-015Atomic Cancellation Preparation and Later Money ReturnProposed
ADR-BIL-BIL-001Billing owns its records and leaves Accounting for its own serviceProposed
ADR-BIL-BIL-002Runs execute on the Data Job Engine, one bulk data job per action kindProposed
ADR-BIL-BIL-003A run keeps its template's resolved instructions from the moment it is madeProposed
ADR-BIL-BIL-004Every run acts under a named person's re-checked authorityProposed
ADR-BIL-BIL-005Status moves are conditional writes and run settlement is eventualProposed
ADR-BIL-BIL-006The dispatcher's minute pass settles runsProposed
ADR-BIL-BIL-007Committed effects stay; recovery reapplies only what did not commitProposed
ADR-BIL-BIL-008A notice names a communications template and holds no messageProposed
ADR-BIL-BIL-009Billing records communication requests, not delivery outcomesProposed
ADR-BIL-BIL-010Billing records carry no custom fieldsProposed
ADR-BIL-BIL-011No billing operation is published to SubmissionsProposed
ADR-BIL-BIL-012Each installment becomes its own invoice under installment-derived keysProposed
ADR-BIL-BIL-013Commerce tenders installment invoices and reports the outcomeProposed
ADR-BIL-BIL-014Configuration saves are versioned whole-record replacementsProposed
ADR-BIL-BIL-015Billing reads CRM names and recipients directlyProposed
ADR-BIL-BIL-016Ended schedules are kept, never deletedProposed
ADR-BIL-BIL-017Recurring occurrences are made ahead on their processing day, once eachProposed
ADR-CMT-CMT-001Record ownership and ordinary mutation boundariesProposed
ADR-CMT-CMT-002One rule decides who serves on a dateProposed
ADR-CMT-CMT-003An edit saves what it carriesProposed
ADR-CMT-CMT-004Individual governance writes use body locks and versionsProposed
ADR-CMT-CMT-005A write's consequences commit with the writeProposed
ADR-CMT-CMT-006Service records end; they are not deleted or undoneProposed
ADR-CMT-CMT-007Bulk changes run as a durable job of per-person transactionsProposed
ADR-CMT-CMT-008The committee is the only custom-field recordProposed
ADR-CMT-CMT-009No operation is published to Submissions yetProposed
ADR-CMT-CMT-010Version twins give history and knowledge-time rostersProposed
ADR-CMT-CMT-011Access is workspace-wide in this releaseProposed
ADR-CMT-CMT-012Enabled attention accompanies relevant writes and sweepsProposed
ADR-CMT-CMT-013Derived authority goes through one Platform function inside the writeProposed
ADR-CMT-CMT-014Outside facts are read from their owners at write timeProposed
ADR-CMT-CMT-015Offers send no e-mailProposed
ADR-CMT-CMT-016Appoint and bulk requests are idempotent for a dayProposed
ADR-CMT-CMT-017Scheduled passes have distinct repeat and failure contractsProposed
ADR-CMT-MTG-001Keep Governance Records in CommitteesProposed
ADR-CMT-MTG-002Share the Governance Transaction BoundaryProposed
ADR-CMT-MTG-003Commit Delivery Work With Business ChangesProposed
ADR-CMT-MTG-004Preserve Fields Omitted From EditsProposed
ADR-CMT-MTG-005Suppress Meeting E-mail Until the Later Delivery PhaseProposed
ADR-CMT-MTG-006Call Recurring Meetings Near Their DateProposed
ADR-CMT-MTG-007Refresh Participants Until the Gathering StartsProposed
ADR-CMT-MTG-008Require Explicit Proxy PermissionProposed
ADR-CMT-MTG-009Use Pasted Video Links for the Deferred MilestoneProposed
ADR-CMT-MTG-010Reuse Shared File PreparationProposed
ADR-CMT-MTG-011Keep Accepted Follow-Ups on the MeetingProposed
ADR-CMT-MTG-012Leave Minutes Approval Authority OpenProposed
ADR-CMT-MTG-013Preserve Decided Governance RecordsProposed
ADR-CMT-MTG-014Evaluate Decisions From Opening SnapshotsProposed
ADR-CMT-MTG-015Apply Carried Consequences AtomicallyProposed
ADR-CMT-MTG-016Deduplicate Delivered Review DecisionsProposed
ADR-CMT-MTG-017Declare Configurable Fields Only for NominationsProposed
ADR-CMT-MTG-018Document the Current Submissions Subject BoundaryProposed
ADR-CMT-MTG-019Authorize Staff and Member Access on the ServerProposed
ADR-CMT-MTG-020Disable Meeting Member and Public Endpoints Until Portal WorkProposed
ADR-CMT-MTG-021Withhold Volunteer Governance AttentionProposed
ADR-CMT-MTG-022Retain Version History for Core Governance RecordsProposed
ADR-CMT-MTG-023Wait for the Staff Surface DecisionProposed
ADR-COM-CAT-001Custom Fields Remain Opt-In and UndeclaredProposed
ADR-COM-CAT-002No Registered Intake PublicationProposed
ADR-COM-CAT-003Accounting Product Ownership and Commerce ExtensionsProposed
ADR-COM-CAT-004Versioned Replacement with Patch ExceptionsProposed
ADR-COM-CAT-005Stable Readable Configuration KeysProposed
ADR-COM-CAT-006Shared Price Calculation and Placement RecalculationProposed
ADR-COM-CAT-007Selecting and Allocating Promotion BenefitsProposed
ADR-COM-CAT-008Atomic Promotion Usage LimitsProposed
ADR-COM-CAT-009Release Usage Without Reversing MoneyProposed
ADR-COM-CAT-010Protected Campaign Terms After First UseProposed
ADR-COM-CAT-011Dependency Failure Policies by Selling ContextProposed
ADR-COM-CAT-012Shared File Processing and Deferred CleanupProposed
ADR-COM-CAT-013Direct Asynchronous Code IssuanceProposed
ADR-COM-CAT-014Campaign History Without Shared Record HistoryProposed
ADR-COM-CAT-015Shared Configuration ProtectionProposed
ADR-COM-CAT-016Public Storefront Visibility and AccessProposed
ADR-COM-CAT-017Schedule Ownership and the Retained APIProposed
ADR-COM-CAT-018Interim Tax Provider and Ownership GapProposed
ADR-COM-CAT-019Recommendation Scope Awaits Product ApprovalProposed
ADR-COM-CAT-020Catalog Product Records Across Commerce FacetsProposed
ADR-COM-CAT-021Fixture Pricing Adapters and Conditional Runtime WiringProposed
ADR-COM-FUL-001Keep delivery coordination separate from application-owned resultsProposed
ADR-COM-FUL-002Retain sale-time conditions until staff explicitly change themProposed
ADR-COM-FUL-003Evaluate current financial facts before recording event consumptionProposed
ADR-COM-FUL-004Commit authorization with dispatch intent and queue a record pointerProposed
ADR-COM-FUL-005Use queue attempts to govern known retries and retain exhaustionProposed
ADR-COM-FUL-006Enforce register transitions and immutable history in the databaseProposed
ADR-COM-FUL-007Commit staff interventions before sending their audit eventsProposed
ADR-COM-FUL-008Start reversal handling with review and leave cancellation settlement to staffProposed
ADR-COM-FUL-009Execute document-requested financial work under stable step keysProposed
ADR-COM-FUL-010Detect operational inconsistency and delegate its repairProposed
ADR-COM-FUL-011Commit physical departure through one local handoff transactionProposed
ADR-COM-FUL-012Resolve retained carrier intent before another purchaseProposed
ADR-COM-FUL-013Maintain stock balances through movement and allocation ledgersProposed
ADR-COM-FUL-014Compete with handoff by fencing the same shipment-line recordsProposed
ADR-COM-FUL-015Delegate carrier calls and credentials to the Integration PlatformProposed
ADR-COM-FUL-016Offer pickup without shipping charge and record counter collectionProposed
ADR-COM-FUL-017Use these records without custom-field extensionsProposed
ADR-COM-FUL-018Keep these operations outside Submissions publicationProposed
ADR-COM-FUL-019Replace configuration at the read version with explicit clearing rulesProposed
ADR-COM-FUL-020Host import routes alongside their collection ownersProposed
ADR-COM-FUL-021Keep stock findings separate pending a product decisionProposed
ADR-COM-FUL-022Retain Commerce history in its own append-only recordsProposed
ADR-COM-ORD-001Five service modules realise OrdersProposed
ADR-COM-ORD-002Accounting owns the money; the order mirrors itProposed
ADR-COM-ORD-003Placement prepares outside a transaction and commits in oneProposed
ADR-COM-ORD-004Placement recomputes the price and refuses a changeProposed
ADR-COM-ORD-005Accounting calls follow the commit under stable keysProposed
ADR-COM-ORD-006An order freezes its checkout policy at placementProposed
ADR-COM-ORD-007After-sale money moves through one adjustment planProposed
ADR-COM-ORD-008Background work runs as one every-minute sweeperProposed
ADR-COM-ORD-009Selling applications plug in through a versioned contractProposed
ADR-COM-ORD-010Orders records carry no custom fieldsProposed
ADR-COM-ORD-011No Orders operation is published to SubmissionsProposed
ADR-COM-ORD-012Rights are drawn through one database functionProposed
ADR-COM-ORD-013Sales are never deleted; history is an append-only trailProposed
ADR-COM-ORD-014Interventions are logged first; the audit event followsProposed
ADR-COM-ORD-015Replacements carry the complete record at the version readProposed
ADR-COM-ORD-016One route set serves portal and console; the caller decides authorityProposed
ADR-CRM-ACT-001One activity is linked to every record it concernsProposed
ADR-CRM-ACT-002Activities and tasks carry no custom fieldsProposed
ADR-CRM-ACT-003Task closing is a dedicated action with its own recordProposed
ADR-CRM-ACT-004Read versions and creation recovery have operation-specific exceptionsProposed
ADR-CRM-ACT-005Replacement carries the complete payload; partial edits are patchesProposed
ADR-CRM-ACT-006A follow-up task commits with its activityProposed
ADR-CRM-ACT-007Workspace-wide lists are queries over datasets, not list routesProposed
ADR-CRM-ACT-008Role offers are decided by Platform's role holding at claim timeProposed
ADR-CRM-ACT-009Workflow task requests use service invocation and current-state repeat handlingProposed
ADR-CRM-ACT-010Overdue attention shares task transactions and uses conditional daily reconciliationProposed
ADR-CRM-ACT-011Activities and tasks outlive the records they concernProposed
ADR-CRM-ACT-012Activity history is written by the database at commit; tasks keep stamps onlyProposed
ADR-CRM-ACT-013Configuration records use immutable configuration identifiers and atomic reorderProposed
ADR-CRM-ACT-014People and roles are Platform references without database keysProposed
ADR-CRM-ACT-015No activities or tasks operation is published to Submissions yetProposed
ADR-CRM-ACT-016Activity files go through the shared record-asset pipelineProposed
ADR-CRM-DQ-001Record ownership and the two Data Quality modulesProposed
ADR-CRM-DQ-002Detect changes after savingProposed
ADR-CRM-DQ-003Use deterministic duplicate matchingProposed
ADR-CRM-DQ-004Audit authorized creation past a blockProposed
ADR-CRM-DQ-005Apply a merge in one transactionProposed
ADR-CRM-DQ-006Let applications apply their own merge changesProposed
ADR-CRM-DQ-007Bind execution to the reviewed previewProposed
ADR-CRM-DQ-008Observe merging through a durable jobProposed
ADR-CRM-DQ-009Preserve absorbed identities for old referencesProposed
ADR-CRM-DQ-010Retain merge originals with workspace historyProposed
ADR-CRM-DQ-011Protect portal access during contact mergingProposed
ADR-CRM-DQ-012Use ordinary record saves for the survivorProposed
ADR-CRM-DQ-013Bound the size of atomic mergesProposed
ADR-CRM-DQ-014Queue re-check windows and retain their outcomesProposed
ADR-CRM-DQ-015Persist bounded review groupsProposed
ADR-CRM-DQ-016Keep Data Quality work records free of custom fieldsProposed
ADR-CRM-DQ-017Declare Data Quality operations unpublished to SubmissionsProposed
ADR-CRM-DQ-018Treat merge plans as shared expiring workProposed
ADR-CRM-DQ-019Provide CRM-owned functions for portal registrationProposed
ADR-CRM-ENT-001Entities Owns the Classification TypesProposed
ADR-CRM-ENT-002The Contact Owns Its AffiliationsProposed
ADR-CRM-ENT-003Whole-record Saves Carry the Complete PayloadProposed
ADR-CRM-ENT-004Changes Use the Version ReadProposed
ADR-CRM-ENT-005Records Commit Before Their ReactionsProposed
ADR-CRM-ENT-006Compensate Platform-held Templates After CRM CommitProposed
ADR-CRM-ENT-007Only Contacts and Organizations Carry Custom FieldsProposed
ADR-CRM-ENT-008Commit Compliance Notice Submissions with StatusProposed
ADR-CRM-ENT-009Dates Follow the Workspace CalendarProposed
ADR-CRM-ENT-010Archive Is Separate from StatusProposed
ADR-CRM-ENT-011Keep Customer Locks and Rhythm Protection ApartProposed
ADR-CRM-ENT-012Resolve Shared Details on ReadProposed
ADR-CRM-ENT-013The Database Writes Record HistoryProposed
ADR-CRM-ENT-014Activate Cross-service Behaviors Through Deployment SwitchesProposed
ADR-CRM-ENT-015No Entities Operation Is Published to SubmissionsProposed
ADR-CRM-REG-001Regions Decides Placement; Entities Stores ItProposed
ADR-CRM-REG-002Placement Follows the Committed Address AsynchronouslyProposed
ADR-CRM-REG-003Policy Changes Move No Record; Staff RecalculateProposed
ADR-CRM-REG-004Recalculation Is a Self-Continuing, Resumable RunProposed
ADR-CRM-REG-005First Enabled Match Wins, With the Fallback LastProposed
ADR-CRM-REG-006The Policy Is Edited Whole or One Rule at a Time Under One LockProposed
ADR-CRM-REG-007Regions and the Policy Carry No Custom FieldsProposed
ADR-CRM-REG-008Region Replacement Carries the Complete PayloadProposed
ADR-CRM-REG-009Changes Are Made Against the Version ReadProposed
ADR-CRM-REG-010Region Locks Need Dedicated, Audited ActionsProposed
ADR-CRM-REG-011A Placement Write Advances the Version Only When the Region MovesProposed
ADR-CRM-REG-012No Regional Operation Is Published to SubmissionsProposed
ADR-CRM-REG-013Every Regional Reference Stays Inside Its WorkspaceProposed
ADR-MBR-MEM-001Separate Configuration From Member HoldingsProposed
ADR-MBR-MEM-002Compute Dated Standing and Cache ListsProposed
ADR-MBR-MEM-003Commit Local Term Effects TogetherProposed
ADR-MBR-MEM-004Derive Grants and Organizational Coverage During WritesProposed
ADR-MBR-MEM-005Give Commerce the Coverage PlanProposed
ADR-MBR-MEM-006Reserve Within Order PlacementProposed
ADR-MBR-MEM-007Recognize Partner Obligations by Their IdentifiersProposed
ADR-MBR-MEM-008Retain Closed Effective CoverageProposed
ADR-MBR-MEM-009Review Plans Before Durable Renewal ExecutionProposed
ADR-MBR-MEM-010Evaluate Officer Reach Through Member UnitsProposed
ADR-MBR-MEM-011Declare Custom Fields Through Shared MetadataProposed
ADR-MBR-MEM-012Record the Absence of Published Intake OperationsProposed
ADR-MBR-MEM-013Publish Through the Current Change-Event TransportProposed
ADR-MBR-MEM-014Settle Attributed History Before CommitProposed
ADR-MBR-MEM-015Publish Validated Monthly VersionsProposed
ADR-MBR-MEM-016Describe Both Configuration Update ModelsProposed
ADR-MBR-MEM-017Resolve Enabled Attention With Its Source WriteProposed
ADR-MBR-MEM-018Read Neighbour Facts and Delegate WritesProposed
ADR-MBR-MEM-019Use the Shared Review EngineProposed
ADR-MBR-MEM-020Delegate Officer Changes With Acting IdentityProposed
ADR-MBR-STR-001Separate Structure, Configuration and Lifecycle CalculationProposed
ADR-MBR-STR-002Serialize Placement Changes and Rebuild Before CommitProposed
ADR-MBR-STR-003Retain Effective and Recorded Parentage Without Future MovesProposed
ADR-MBR-STR-004Apply the Recorded Atomic Membership MergeProposed
ADR-MBR-STR-005Share Accounting Identity for Membership OfferingsProposed
ADR-MBR-STR-006Describe the Two-Step Offering Save and Its GapProposed
ADR-MBR-STR-007Reference Commerce Ordering ProfilesProposed
ADR-MBR-STR-008Keep Pure Lifecycle Decisions IsolatedProposed
ADR-MBR-STR-009Apply Custom-Field Opt-In to UnitsProposed
ADR-MBR-STR-010Record the Absence of Submissions BindingsProposed
ADR-MBR-STR-011Make Version Requirements Explicit Per OperationProposed
ADR-MBR-STR-012Describe Both Replacement and Partial-Save SemanticsProposed
ADR-MBR-STR-013Publish Reparenting Inside the Placement TransactionProposed
ADR-MBR-STR-014Retire Referenced Records and Respect Deletion GuardsProposed
ADR-MBR-STR-015Keep Setup Permissions at Workspace ScopeProposed
ADR-MBR-STR-016Defer Ancestry Rebuilding During Bulk LoadsProposed
ADR-MBR-STR-017Retain Stable Configuration and Product IdentitiesProposed
ADR-MBR-STR-018Remove Protected Versions Through the Owner FunctionProposed
ADR-MKT-MKT-001Interactive Evaluation Retains the Requester’s Read AuthorityProposed
ADR-MKT-MKT-002Saved-query Copies Change Through Deliberate AdoptionProposed
ADR-MKT-MKT-003Full Counting Uses a Durable Evaluation JobProposed
ADR-MKT-MKT-004Evaluation Failures Remain Distinct from Empty ReachProposed
ADR-MKT-MKT-005Audience Size Limits Are Visible and Fail ClosedProposed
ADR-MKT-MKT-006Marketing Updates Preserve Omitted Fields Pending Product ReviewProposed
ADR-MKT-MKT-007Audience Success History Commits with Its MutationProposed
ADR-MKT-MKT-008Marketing Records Have No Custom-field SurfaceProposed
ADR-MKT-MKT-009Current Marketing Eligibility Uses CRM Global Opt-outProposed
ADR-MKT-MKT-010Recipient Relationship Declarations Remain Local During IntegrationProposed
ADR-MKT-MKT-011Evaluation Reads Owner Suppressions and Aliases DirectlyProposed
ADR-MKT-MKT-012Audience Exclusions Resolve One Level of ContactsProposed
ADR-MKT-MKT-013Archive Preserves References While Closing Staff MutationProposed
ADR-MKT-MKT-014List Contact References Are Resolved and Reassigned LaterProposed
ADR-MKT-MKT-015Recipient Computation Is Shared Without PersistenceProposed
ADR-MKT-MKT-016Current Marketing Operations Have No Submissions PublicationProposed
ADR-MKT-MKT-017The Probe Uses Owned Templates on Platform’s Marketing LaneProposed
ADR-MKT-MKT-018Workspace Policies Isolate Ordinary Marketing RecordsProposed
ADR-MKT-MKT-019Manual Membership Transactions Maintain Stored Row TotalsProposed
ADR-PFM-CSH-001Presentation Ownership Stays With the ShellProposed
ADR-PFM-CSH-002Security Context Gates Console MountingProposed
ADR-PFM-CSH-003Workspace Addresses Require Strict EntryProposed
ADR-PFM-CSH-004Shared Builders Define Console DestinationsProposed
ADR-PFM-CSH-005Application Gating Precedes Page PermissionsProposed
ADR-PFM-CSH-006Application Lists Refresh as SnapshotsProposed
ADR-PFM-CSH-007Navigation Visibility Supplements AuthorizationProposed
ADR-PFM-CSH-008Metadata Supplies Readable Record PlacementsProposed
ADR-PFM-CSH-009Workspace Switching Retains Resource ContextProposed
ADR-PFM-CSH-010HQ and Workspace Navigation Use Separate ModesProposed
ADR-PFM-CSH-011Compatibility Mapping Remains TemporaryProposed
ADR-PFM-CSH-012Rendering Pages Select Their WidthProposed
ADR-PFM-CSH-013The Shell Owns No Business SaveProposed
ADR-PFM-CSH-014Presentation Objects Declare No Custom FieldsProposed
ADR-PFM-CSH-015Consumed Reads Are Excluded From IntakeProposed
ADR-PFM-DJE-001Shared engine with service-owned storageProposed
ADR-PFM-DJE-002Frozen input and transactional receiptsProposed
ADR-PFM-DJE-003Fingerprint approval and counted delete confirmationProposed
ADR-PFM-DJE-004Isolate record refusals and retain successful changesProposed
ADR-PFM-DJE-005Rollback through a guarded compensating jobProposed
ADR-PFM-DJE-006Capture and recheck record versionsProposed
ADR-PFM-DJE-007Durable producer identity mappingProposed
ADR-PFM-DJE-008Interactive and file lanes share the batch runnerProposed
ADR-PFM-DJE-009Capacity-scaled admission across jobs and workspacesProposed
ADR-PFM-DJE-010Staff-driven data runsProposed
ADR-PFM-DJE-011Keep partial migration loads and recover by resetProposed
ADR-PFM-DJE-012Direct multipart upload with recorded object identityProposed
ADR-PFM-DJE-013Capacity decisions with hysteresis and an optional emergency switchProposed
ADR-PFM-DJE-014Daily owner-authorized partition maintenanceProposed
ADR-PFM-DJE-015No custom fields on engine-owned objectsProposed
ADR-PFM-DJE-016No operation published to SubmissionsProposed
ADR-PFM-DJE-017Workspace isolation and explicit application grantsProposed
ADR-PFM-DJE-018Domain saves own history and change eventsProposed
ADR-PFM-DJE-019Platform executes small jobs within requestsProposed
ADR-PFM-DJE-020Decided evidence retention exceeds implemented purgingProposed
ADR-PFM-ELG-001Eligibility is a Platform module over one shared rules grammarProposed
ADR-PFM-ELG-002Platform hosts evaluation until a consumer package is publishedProposed
ADR-PFM-ELG-003Answers are three-valued and each use decides uncertaintyProposed
ADR-PFM-ELG-004Applications declare vocabularies by complete manifest at deploymentProposed
ADR-PFM-ELG-005Published versions are immutable and a rollback is a new versionProposed
ADR-PFM-ELG-006A publish that breaks followers is refused unless forcedProposed
ADR-PFM-ELG-007Decisions are append-only, sampled for display and kept thirteen monthsProposed
ADR-PFM-ELG-008Caches are disposable, keyed by content and bounded in stalenessProposed
ADR-PFM-ELG-009Security owns derived roles; eligibility answers and queues rechecksProposed
ADR-PFM-ELG-010Bulk and scheduled work runs as durable jobs per workspaceProposed
ADR-PFM-ELG-011Responsibilities are their own module and grant no accessProposed
ADR-PFM-ELG-012Role defaults are rows the workspace may removeProposed
ADR-PFM-ELG-013Attention items are stored and written at sourceProposed
ADR-PFM-ELG-014Audiences are resolved when a person readsProposed
ADR-PFM-ELG-015Classes are fixed by the provider and required attention cannot be dismissedProposed
ADR-PFM-ELG-016Attention sends nothing itself; reminders go through Notifications and start offProposed
ADR-PFM-ELG-017Committed writes survive follow-up failures with partial scheduled repairProposed
ADR-PFM-ELG-018Decisions and attention items use monthly partitions with thirteen months keptProposed
ADR-PFM-ELG-019No record of this module carries custom fieldsProposed
ADR-PFM-ELG-020No operation of this module is published to SubmissionsProposed
ADR-PFM-ELG-021Attention is console-only while the portal is heldProposed
ADR-PFM-ELG-022Field-changing writes carry the version readProposed
ADR-PFM-INT-001Three source modules, one owner per recordProposed
ADR-PFM-INT-002A connection changes state only through named transitionsProposed
ADR-PFM-INT-003Bindings choose the account; money never falls backProposed
ADR-PFM-INT-004One execution outlives its attempts and owns the request identityProposed
ADR-PFM-INT-005Uncertain outcomes are looked up, never resent or compensatedProposed
ADR-PFM-INT-006Settlement records one completion eventProposed
ADR-PFM-INT-007A money call that cannot finish in budget is stoppedProposed
ADR-PFM-INT-008Credentials live only in secret storage and are lent brieflyProposed
ADR-PFM-INT-009Background work follows the queued-work standard, delivered at least onceProposed
ADR-PFM-INT-010History is the integration trail and the security trailProposed
ADR-PFM-INT-011Accepted access is checked where it is usedProposed
ADR-PFM-INT-012Edits carry the version read; lifecycle actions are guarded by stateProposed
ADR-PFM-INT-013No integration-area record carries custom fieldsProposed
ADR-PFM-INT-014No integration-area operation is published to SubmissionsProposed
ADR-PFM-INT-015Registries are written only by deploy-time manifestsProposed
ADR-PFM-INT-016Platform keeps customization configuration; hosts execute itProposed
ADR-PFM-INT-017Hosts execute workflow actions; Platform keeps shared configurationProposed
ADR-PFM-INT-018Readers see everything except secretsProposed
ADR-PFM-INT-019Workspace records are separated by the database; registries are globalProposed
ADR-PFM-INT-020Workspace deletion removes protected history before ordinary rowsProposed
ADR-PFM-LLM-001Centralize Model Execution and Keep Answers With Their FeatureProposed
ADR-PFM-LLM-002Record Before Admission and Reserve With One Conditional UpdateProposed
ADR-PFM-LLM-003Attempt Settlement With Usage, Estimate or ReleaseProposed
ADR-PFM-LLM-004Recover Stale Work Through a Later SweepProposed
ADR-PFM-LLM-005Publish Immutable Routing and Price History at DeploymentProposed
ADR-PFM-LLM-006Create Local Monthly Allowance Accounts When NeededProposed
ADR-PFM-LLM-007Evaluate Temporary Grants at Request TimeProposed
ADR-PFM-LLM-008Commit Control Changes With Their Security AuditProposed
ADR-PFM-LLM-009Replace Limits at the Inspected VersionProposed
ADR-PFM-LLM-010Keep Duplicate Creates Visible Until Replay Protection ExistsProposed
ADR-PFM-LLM-011Attempt Administrator Notices After Commit With Bounded RetryProposed
ADR-PFM-LLM-012Apply Redacted Capture Policy Through Narrow Audited AccessProposed
ADR-PFM-LLM-013Use Daily Aggregates for HQ History and Scoped Reads for Live DetailProposed
ADR-PFM-LLM-014Show Credit Capacity to Customers and Monetary Cost to HQProposed
ADR-PFM-LLM-015Keep AI Objects Outside Custom-Field RegistrationProposed
ADR-PFM-LLM-016Exclude These Operations From Configurable IntakeProposed
ADR-PFM-LLM-017Leave the Durable Jazz AI Boundary OpenProposed
ADR-PFM-MTD-001Deploy-time registration with retained definitionsProposed
ADR-PFM-MTD-002Registry-based configuration eligibilityProposed
ADR-PFM-MTD-003Permanent field identity and widening constraintsProposed
ADR-PFM-MTD-004Purpose-governed layout documentsProposed
ADR-PFM-MTD-005Shared typed persistence for custom recordsProposed
ADR-PFM-MTD-006Read-only records under inactive definitionsProposed
ADR-PFM-MTD-007Record identity scoped to its objectProposed
ADR-PFM-MTD-008Transactional capture with later deliveryProposed
ADR-PFM-MTD-009Transactional deletion with dependent eventsProposed
ADR-PFM-MTD-010Platform relationships with dated membershipProposed
ADR-PFM-MTD-011Version-checked complete record replacementProposed
ADR-PFM-MTD-012Explicit boundaries for partial savesProposed
ADR-PFM-MTD-013Uploader-bound staging and asset preparationProposed
ADR-PFM-MTD-014Current exclusion from SubmissionsProposed
ADR-PFM-MTD-015Commit-time history capture that refuses incomplete writesProposed
ADR-PFM-MTD-016Incremental data-job loading through standard writesProposed
ADR-PFM-NOT-001Notifications Is a Platform Module Beside CommunicationsProposed
ADR-PFM-NOT-002Staff Notices and Association E-mail Are Separate ModelsProposed
ADR-PFM-NOT-003Producers Publish Inside Their Own Transaction Through an Insert-Only RoleProposed
ADR-PFM-NOT-004The Queue Holds Only Work and SQS Owns Every RetryProposed
ADR-PFM-NOT-005A Submission Is Validated Whole and Travels CompleteProposed
ADR-PFM-NOT-006The Request Object Is Written Inside the Caller's TransactionProposed
ADR-PFM-NOT-007Definitions Are Registered at Deploy and Retired, Never DeletedProposed
ADR-PFM-NOT-008Audiences Resolve at Processing, Inside the Workspace, Capped at Two HundredProposed
ADR-PFM-NOT-009Withdrawal Ends Unsent Work and Never Recalls What LeftProposed
ADR-PFM-NOT-010An Uncertain Hand-off Waits Out a Fifteen-Minute WindowProposed
ADR-PFM-NOT-011Rhythm HQ Alerts Are Hard-Coded Slack Deliveries in a System ScopeProposed
ADR-PFM-NOT-012Console, E-mail and Text Are Native; Customer Chat Goes Through IntegrationsProposed
ADR-PFM-NOT-013Preferences and Workspace Settings Are Stored but Not Applied YetProposed
ADR-PFM-NOT-014The Person Is Always the Signed Caller; Support Reads Need a GrantProposed
ADR-PFM-NOT-015Notification and Communication Records Carry No Custom FieldsProposed
ADR-PFM-NOT-016No Notification or Communication Operation Is Published to SubmissionsProposed
ADR-PFM-NOT-017Dispatch, Provider Delivery and Engagement Are Separate FactsProposed
ADR-PFM-NOT-018A Record Owns Its Template and Composes It Through Its Own APIProposed
ADR-PFM-NOT-019Three Rendering Modes Decide Who Supplies the ContentProposed
ADR-PFM-NOT-020Purpose-Classified Lanes Keep Transactional Mail Ahead of Bulk MailProposed
ADR-PFM-OPS-001Execution, record and meaning of a job have three ownersProposed
ADR-PFM-OPS-002A job is recorded with its business change and started after the commitProposed
ADR-PFM-OPS-003A job kind declares its failure consequence once, applied from both settlement pathsProposed
ADR-PFM-OPS-004Requester notices favour at-least-once delivery over strict once-onlyProposed
ADR-PFM-OPS-005Customer, workspace and Rhythm HQ monitors are separate declarations of one readProposed
ADR-PFM-OPS-006Other services’ jobs are read through published views, read-onlyProposed
ADR-PFM-OPS-007Record activity is an append-only, workspace-isolated store separate from the security historyProposed
ADR-PFM-OPS-008A visit’s identity is minted by the console and its attribution by the serverProposed
ADR-PFM-OPS-009Recently Viewed lists are answered by the query layer, not by the activity storeProposed
ADR-PFM-OPS-010Licence overrides are revoked, never edited, and a withhold beats everythingProposed
ADR-PFM-OPS-011A licensing decision commits first and later steps never undo itProposed
ADR-PFM-OPS-012A company’s contract copy is replaced whole after a complete read, or not at allProposed
ADR-PFM-OPS-013Availability is licence and readiness together, computed once and enforced by the dispatcherProposed
ADR-PFM-OPS-014Licensing records carry no row-level policy; staff-only routes keep them privateProposed
ADR-PFM-OPS-015The module’s records carry no custom fieldsProposed
ADR-PFM-OPS-016No operation of this module is published to SubmissionsProposed
ADR-PFM-OPS-017The commercial source is read-only and off until its key exists; the nightly read is authoritativeProposed
ADR-PFM-QRY-001Five service owners realize six planning conceptsProposed
ADR-PFM-QRY-002Source applications retain their business recordsProposed
ADR-PFM-QRY-003Person-requested work uses current person accessProposed
ADR-PFM-QRY-004The query executor is shared across query consumersProposed
ADR-PFM-QRY-005Queue workers and durable jobs have distinct execution boundariesProposed
ADR-PFM-QRY-006Query delivery is pinned; report delivery uses the current presentationProposed
ADR-PFM-QRY-007Retry transient failures and retain external effectsProposed
ADR-PFM-QRY-008Presentation sharing respects source audiencesProposed
ADR-PFM-QRY-009Audience settings do not form a lifecycleProposed
ADR-PFM-QRY-010Search generation ledgers do not isolate provider visibilityProposed
ADR-PFM-QRY-011Organization lookup retains its disputed implemented gateProposed
ADR-PFM-QRY-012Snapshot versions share a ledger and publish after validationProposed
ADR-PFM-QRY-013Workspace exports admit requests without a generation runnerProposed
ADR-PFM-QRY-014Custom-table publication requires validation configurationProposed
ADR-PFM-QRY-015The application validates model-proposed queriesProposed
ADR-PFM-QRY-016Definition replacement uses the version previously readProposed
ADR-PFM-QRY-017Descriptions use change stamps as cache keysProposed
ADR-PFM-QRY-018Navigation retains a bounded identity windowProposed
ADR-PFM-QRY-019Source custom fields do not extend this module’s objectsProposed
ADR-PFM-QRY-020Queries operations remain unpublished to SubmissionsProposed
ADR-PFM-SEC-001Workspace decisions and participant executionProposed
ADR-PFM-SEC-002User Account aggregatesProposed
ADR-PFM-SEC-003Permanent readable customer and workspace identityProposed
ADR-PFM-SEC-004Separate business status and lifecycleProposed
ADR-PFM-SEC-005Durable execution after committed intentProposed
ADR-PFM-SEC-006Retirement boundary and forward recoveryProposed
ADR-PFM-SEC-007Scoped authority with bounded cached contextProposed
ADR-PFM-SEC-008Provider synchronization and durable removalProposed
ADR-PFM-SEC-009Recorded staff customer entryProposed
ADR-PFM-SEC-010Release-controlled shared definitionsProposed
ADR-PFM-SEC-011No custom-field capabilityProposed
ADR-PFM-SEC-012Submissions publication exclusionsProposed
ADR-PFM-SEC-013Versioned record replacement contractProposed
ADR-PFM-SEC-014Dedicated security history and refusal recordingProposed
ADR-PFM-SEC-015Source-owned contact-derived accessProposed
ADR-PFM-SEC-016Confirmed portal self-registrationProposed
ADR-PFM-TNL-001Lifecycle and Workspace Administration BoundariesProposed
ADR-PFM-TNL-002Controlled Lifecycle WritesProposed
ADR-PFM-TNL-003Request-Specific AvailabilityProposed
ADR-PFM-TNL-004Durable Lifecycle ExecutionProposed
ADR-PFM-TNL-005Static Participant Planning and Platform EnablementProposed
ADR-PFM-TNL-006Retained Construction Work After FailureProposed
ADR-PFM-TNL-007Ledgered Defaults and Baseline ReconciliationProposed
ADR-PFM-TNL-008Reversible Decisions Before DestructionProposed
ADR-PFM-TNL-009Internal Notice ObligationsProposed
ADR-PFM-TNL-010Batched Removal and Declared-Resource VerificationProposed
ADR-PFM-TNL-011Retained Evidence and Restore ReapplicationProposed
ADR-PFM-TNL-012Classified Initial-Load ResetProposed
ADR-PFM-TNL-013Separate Staff Lifecycle AuthoritiesProposed
ADR-PFM-TNL-014Custom Fields Remain UndeclaredProposed
ADR-PFM-TNL-015Lifecycle Operations Outside Configurable IntakeProposed
ADR-PFM-TNL-016Dedicated Deletion CommandsProposed
ADR-PFM-TNL-017Lifecycle Evidence and Removal CaptureProposed
ADR-PFM-TNL-018Application-Owned Export ContributionsProposed
ADR-SUB-SUB-001Submissions records carry no custom fieldsProposed
ADR-SUB-SUB-002No engine operation is published as a Submission Form bindingProposed
ADR-SUB-SUB-003One macroservice of five modules joined by seam operations and a fixed lock orderProposed
ADR-SUB-SUB-004Published versions are frozen and every application stays pinned to its versionProposed
ADR-SUB-SUB-005A stage completes exactly once under row locks backed by partial unique indexesProposed
ADR-SUB-SUB-006Decisions reach owners at least once through a queued pointer, acknowledgement and reconciliationProposed
ADR-SUB-SUB-007Blind review is enforced by server-side projectionProposed
ADR-SUB-SUB-008A reviewer’s reach comes from participation, not a staff permissionProposed
ADR-SUB-SUB-009Scoring sheets, teams and reviewer rules belong to one process; reuse is a copyProposed
ADR-SUB-SUB-010Configured follow-up uses the shared Workflow Action Engine with incomplete failure isolationProposed
ADR-SUB-SUB-011Lists are replaced whole at the version readProposed
ADR-SUB-SUB-012Ending an application cancels pending work rather than reversing completed effectsProposed
ADR-SUB-SUB-013The action log is the engine’s historyProposed
ADR-SUB-SUB-014Contributors reach one request through a hashed private link with a neutral refusalProposed
ADR-SUB-SUB-015Stages resolve inline in the triggering transactionProposed
ADR-SUB-SUB-016Conditions the engine cannot evaluate refuse publicationProposed
ADR-SUB-SUB-017The standalone engine is the interim form of Platform’s reviews moduleProposed
ADR-SUB-SUB-018Owners reach intake and status through trusted-invoke functions authorised by cloud roleProposed
ADR-SUB-SUB-019The console saves a process as a sequence of calls without a server transactionProposed
ADR-SUB-SUB-020Files stay in Platform; applications hold prepared references behind a scanning portProposed
ADR-WEB-WEB-001Custom fields require product designationProposed
ADR-WEB-WEB-002Submission publication is declared per operationProposed
ADR-WEB-WEB-003The site registry stays with PlatformProposed
ADR-WEB-WEB-004Delivery runs one customer application per environmentProposed
ADR-WEB-WEB-005Editor entry preserves console identity and site scopeProposed
ADR-WEB-WEB-006Editorial publication refreshes content without rebuildingProposed
ADR-WEB-WEB-007Draft editing and publication use separate authorityProposed
ADR-WEB-WEB-008The page tree determines addresses and redirectsProposed
ADR-WEB-WEB-009Named navigation places connect layouts and menusProposed
ADR-WEB-WEB-010Application edits use revisioned website changesProposed
ADR-WEB-WEB-011Replacement writes carry complete owned valuesProposed
ADR-WEB-WEB-012Publication separates confirmation from staff reviewProposed
ADR-WEB-WEB-013History limits retain existing entriesProposed
ADR-WEB-WEB-014Authenticated reports and reconciliation drive progressProposed
ADR-WEB-WEB-015Customer recovery restores release and template designProposed
ADR-WEB-WEB-016Committed partial work remains available for diagnosisProposed
ADR-WEB-WEB-017Hostname ownership establishes visitor routing identityProposed
ADR-WEB-WEB-018Assistant tools preserve the caller’s existing authorityProposed
ADR-WEB-WEB-019Integration gates preserve infrastructure readinessProposed
ADR-WEB-WEB-020Audit persistence follows the action ownerProposed
ADR-WEB-WEB-021The content runner delivers publication refresh workProposed
ADR-WEB-WEB-022Portal adapters defer record authorization to its ownerProposed
ADR-WEB-WEB-023Existing histories remain separate from field-history captureProposed
ADR-WEB-WEB-024Cross-service references use scoped reads without foreign keysProposed