Queries planning findings and questions
Findings
The entries retain unresolved product choices, implementation limits and corrections made during examination. The examination report records which gaps are corrected and which still require a decision or proof.
| id | severity | statement | affects | evidence | kind |
|---|---|---|---|---|---|
FND-PFM-QRY-001 | medium | The original registry mixed this module with data-job material and omitted relevant records and console components. The module charter now identifies the query scope and leaves data-job ownership with operations. | MOD-PFM-QRY | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-002 | high | Quick Search authorizes organization lookup through contact-read access. The recorded organization-search decision later requires organization read and query access. These decisions conflict, so the intended gate needs Andrew’s ruling. | BR-CAP-PFM-QRY-016-02, CAP-PFM-QRY-016, OQ-PFM-QRY-001 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-003 | medium | The standalone Search page filters locally supplied demonstration records. The header lookup uses the real search integration. The separate page can therefore present sample records as if they were live results. | CAP-PFM-QRY-016 | Source listed in frontmatter | defect |
FND-PFM-QRY-004 | medium | Workspace export admission is implemented, but the current module does not generate packages. Download, cancellation, early deletion and delivery retry remain unavailable. The accepted design also includes later protections and delivery behavior that the foundation does not enforce. | BR-CAP-PFM-QRY-018-08, BR-CAP-PFM-QRY-018-12, BR-CAP-PFM-QRY-018-13, CAP-PFM-QRY-018, JNY-PFM-QRY-006 | Source listed in frontmatter | debt |
FND-PFM-QRY-005 | low | The permission catalog includes seven unused standard actions: four query write actions and three Quick Search configuration actions. These declarations do not establish corresponding supported routes. | CAP-PFM-QRY-002, CAP-PFM-QRY-017 | Source listed in frontmatter | debt |
FND-PFM-QRY-006 | medium | The reporting milestone remains in progress and its last recorded cumulative run is incomplete. Approved decisions establish intent for the catalog and sharing work; they do not establish acceptance of the implementation. | CAP-PFM-QRY-011, CAP-PFM-QRY-012, JNY-PFM-QRY-001 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-007 | low | Older descriptions use the saved-query use permission for library access. The newer read tier and route declarations require the read permission for listing, opening and running, so a role carrying use alone is insufficient. | BR-CAP-PFM-QRY-006-03, BR-CAP-PFM-QRY-011-02 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-008 | medium | The milestone records joined-dataset checking as unresolved for report discovery. The catalog can include a presentation whose source later fails during execution. The corrected rules describe the narrower observed filter. | BR-CAP-PFM-QRY-011-03, BR-CAP-PFM-QRY-012-08 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-009 | low | The read tier can export executable query results but cannot request report rendering. The milestone’s broader wording about preventing exports leaves the intended distinction unresolved. | BR-CAP-PFM-QRY-014-01, BR-CAP-PFM-QRY-013-01, OQ-PFM-QRY-002 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-010 | medium | Report rendering and report scheduling exist beyond the initial catalog milestone’s scope. Their implementation does not supply approval for every later reporting outcome; unconfirmed behavior remains proposed. | CAP-PFM-QRY-013, CAP-PFM-QRY-015, BR-CAP-PFM-QRY-015-12 | Source listed in frontmatter | debt |
FND-PFM-QRY-011 | low | Index configuration and rebuild operations have backend surfaces, and snapshot months have an available-period API. No dedicated console configuration screen or report period-picker integration is established by the scoped pages. | CAP-PFM-QRY-017, CAP-PFM-QRY-019 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-012 | medium | The language-size limits come from the semantic query design and a shared request schema outside the pinned repositories examined here. No cited in-scope test establishes those limits, so their rule remains documented and its acceptance scenario remains proposed. | BR-CAP-PFM-QRY-002-15 | Source listed in frontmatter | debt |
FND-PFM-QRY-013 | low | The older scheduling record and the public download implementation disagree about the download route and expired-link response. The service’s debt record describes an invalid-link page that still uses a successful HTTP status. | BR-CAP-PFM-QRY-014-09 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-014 | low | The saved-query record makes a broad statement that version headers are unused. Explorer preference replacement provides a counterexample by using a version header. | BR-CAP-PFM-QRY-009-11 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-015 | low | The browser journey identifies a duplicate pause label after loss of schedule-owner access. Its assertion asks for the explanation to appear once; this examination does not establish that the defect has been repaired. | CAP-PFM-QRY-015 | Source listed in frontmatter | defect |
FND-PFM-QRY-016 | medium | An existing browser test proves that executable assertions were written. It does not prove a successful run at these source revisions. The recorded reporting run remains incomplete and some journeys identify console defects. | JNY-PFM-QRY-001, JNY-PFM-QRY-002, JNY-PFM-QRY-004, MOD-PFM-QRY | Source listed in frontmatter | debt |
FND-PFM-QRY-017 | low | Several required proofs still have proposed acceptance scenarios without executable bindings. The unbound scenarios are explicit proof obligations; their presence does not establish passing behavior. | BR-CAP-PFM-QRY-002-15, BR-CAP-PFM-QRY-005-08, BR-CAP-PFM-QRY-005-11, BR-CAP-PFM-QRY-010-01, BR-CAP-PFM-QRY-010-08, BR-CAP-PFM-QRY-012-08, BR-CAP-PFM-QRY-018-12, BR-CAP-PFM-QRY-018-13, BR-CAP-PFM-QRY-019-09 | Source listed in frontmatter | debt |
FND-PFM-QRY-018 | low | Query generation has a separate permission and allowance mechanism, but the cited query material supplies no product approval for the complete assisted-authoring outcome. The capability retains proposed intent. | CAP-PFM-QRY-003 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-019 | low | The earlier report inventory includes accounting calculations and period behavior outside this module’s ownership. Those inventory entries remain for Accounting; only the generic presentation and delivery concerns belong here. | MOD-PFM-QRY, CAP-PFM-QRY-011 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-020 | low | Built-in report catalog filtering belongs to console behavior. The module’s record describes the intended hiding rule, but the scoped evidence does not independently prove every built-in presentation is hidden correctly. | BR-CAP-PFM-QRY-011-14 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-021 | low | The export coverage implementation was reconstructed after an ignore rule lost its source. The repair record preserves that history; current fingerprint choices cannot be treated as proof of the original implementation. | BR-CAP-PFM-QRY-018-10 | Source listed in frontmatter | debt |
FND-PFM-QRY-022 | low | The Quick Search record describes broad rebuild scans, missing fan-out indexing, delayed coalesced targets, a limited field-retirement pass and shared-role secret access. Its production-provider limitation is a documented condition at the source revision, not a newly inspected deployment state. | CAP-PFM-QRY-016, CAP-PFM-QRY-017 | Source listed in frontmatter | debt |
FND-PFM-QRY-023 | medium | The requested planning brief is absent from the starting documentation revision. Its original discovery instructions therefore remain unavailable to this examination. | MOD-PFM-QRY | Source listed in frontmatter | undocumented |
FND-PFM-QRY-024 | medium | The accepted custom-table phase excludes assignment pins and reverse joins into custom tables. Later code implements those behaviors, but that acceptance citation does not confirm their intent. | CAP-PFM-QRY-005, BR-CAP-PFM-QRY-005-09, BR-CAP-PFM-QRY-005-13 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-025 | medium | Navigation retains a bounded identifier window. Extending or rebuilding it queries again, so the implementation does not guarantee an immutable entire list or continued execution after access is withdrawn. | CAP-PFM-QRY-010, JNY-PFM-QRY-003 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-026 | medium | The report catalog evaluates visible sources and base-dataset access without validating the full query. A dashboard with no sources passes that check. Catalog visibility therefore does not guarantee successful result execution. | CAP-PFM-QRY-011, CAP-PFM-QRY-012 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-027 | medium | The initial draft lacked an outcome for internal dated condition evaluation and explicit rules for grouped calculations, SQL safety, custom-table revalidation, generation recovery and console lookup timing. This examination adds a capability and acceptance set for the distinct outcome and rule coverage for the remaining facets. | CAP-PFM-QRY-002, CAP-PFM-QRY-005, CAP-PFM-QRY-020 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-028 | low | The initial claim of complete backend suite binding omitted the report-export API file. The report-rendering acceptance set now binds an existing permission-refusal case from that suite. | ATS-PFM-QRY-013, MOD-PFM-QRY | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-029 | medium | The original search configuration binding proves that a rebuild job is returned. It does not prove publication or lookup through the added field. The complete interaction is now a proposed browser scenario. | ATS-PFM-QRY-017, AS-JNY-PFM-QRY-005-01 | Source listed in frontmatter | debt |
FND-PFM-QRY-030 | low | The charter maps 115 operations, but the route declarations hold 121: deprecating, disabling and restoring a custom query table, and the queries, Explorer and snapshots health routes, are unmapped. The lifecycle routes also check no starting state, so restoring an active table is accepted and recorded as a restore. The service contract covers every route. | MOD-PFM-QRY, SVC-PFM-QRY-queries, STATE-PFM-QRY-001, CAP-PFM-QRY-005 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-031 | low | Two Rhythm HQ console screens administer custom query tables, but the charter’s hosted screens and the registry’s console paths omit them. The design adds screen contracts for both; the charter should list them at its next revision. | MOD-PFM-QRY, SCR-PFM-QRY-017, SCR-PFM-QRY-018 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-032 | high | An admitted workspace data export stays queued because no dispatcher or generation job is deployed, and cancellation answers not implemented. Only one execution may be queued or running, so the first Export now in a workspace blocks every later request with no recovery available to the customer. | CAP-PFM-QRY-018, BR-CAP-PFM-QRY-018-06, BR-CAP-PFM-QRY-018-08, WF-PFM-QRY-019, STATE-PFM-QRY-009, ADR-PFM-QRY-013, OQ-PFM-QRY-003 | Source listed in frontmatter | defect |
FND-PFM-QRY-033 | medium | Destination bindings to storage connections are held in process memory until the Integration Platform’s binding store merges. A destination row and its audit event are durable, but the binding id it records does not survive a restart, so no delivery could rely on it. | SVC-PFM-QRY-data-exports, STATE-PFM-QRY-011, BR-CAP-PFM-QRY-018-05 | Source listed in frontmatter | debt |
FND-PFM-QRY-034 | low | Export definitions declare paused and suspended statuses and admission refuses a suspended definition, but nothing sets either status, and the staff operate permission reaches no route. The suspension guard protects a state the product cannot enter. | SVC-PFM-QRY-data-exports, DOM-PFM-QRY-004, CAP-PFM-QRY-018 | Source listed in frontmatter | debt |
FND-PFM-QRY-035 | medium | The export concept joins query and report files with complete workspace packages. They have different service modules, permissions, storage, retention and lifecycles, so one domain object carries two largely independent designs. | CON-PFM-QRY-004, DOM-PFM-QRY-004, ADR-PFM-QRY-001, OQ-PFM-QRY-004 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-036 | low | The query concept spans two service modules: saved queries, recipes and generations in queries, and Explorer views, preferences and navigation sessions in explorer. The design keeps one domain object and records facet ownership. | CON-PFM-QRY-002, DOM-PFM-QRY-002, SVC-PFM-QRY-explorer, ADR-PFM-QRY-001 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-037 | low | The planning concepts give queries a draft, private and shared lifecycle and reports a private, shared and deleted lifecycle. These are audience values and a removal, not states with transitions, so the design records no state models for them. | CON-PFM-QRY-002, CON-PFM-QRY-003, DOM-PFM-QRY-002, DOM-PFM-QRY-003, ADR-PFM-QRY-009 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-038 | medium | A report schedule run waits inside the schedule consumer for the renderer, polling for up to twelve minutes. Only three consumers run at once, so a slow renderer backlog can delay every scheduled query delivery in the environment. | WF-PFM-QRY-008, WF-PFM-QRY-007, STATE-PFM-QRY-008 | Source listed in frontmatter | debt |
FND-PFM-QRY-039 | low | Quick Search provisions every record type when a workspace is created, as well as on first search access. The planning rule describes only the first-search path, so its description of when indexing begins is incomplete. | BR-CAP-PFM-QRY-016-06, WF-PFM-QRY-014, WF-PFM-QRY-021 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-040 | medium | Query and report files stay in the Rhythm 1.0 bucket for up to thirty days after a workspace is deleted, because the purge removes only the rows. The bucket’s own lifecycle rule, outside Platform’s control, is the only retention mechanism. | WF-PFM-QRY-021, DOM-PFM-QRY-004, BR-CAP-PFM-QRY-014-08 | Source listed in frontmatter | debt |
FND-PFM-QRY-041 | low | Explorer views, navigation and selection are used by list screens owned by the applications that own the records. This module therefore has no Explorer screen contract, and those applications’ list screen contracts should name the Explorer operations they call. | SVC-PFM-QRY-explorer, CAP-PFM-QRY-009, CAP-PFM-QRY-010 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-042 | medium | Production names no validation workspace, by Andrew’s decision of 2026-10-12. Custom query tables therefore cannot be analysed, previewed, published or revalidated there, and the staff outcome is available only in development. The planning rule covers absent configuration but not this production consequence. | CAP-PFM-QRY-005, BR-CAP-PFM-QRY-005-05, WF-PFM-QRY-009, WF-PFM-QRY-010, ADR-PFM-QRY-014 | Source listed in frontmatter | undocumented |
FND-PFM-QRY-043 | low | The snapshot routes run on the jobs module’s HTTP function rather than a snapshots function. The contract records this deployment boundary because operational ownership of those routes sits with the jobs function. | SVC-PFM-QRY-snapshots | Source listed in frontmatter | undocumented |
FND-PFM-QRY-044 | medium | The requested design brief is absent from the starting documentation revision. Examination uses the authoring contract, module charter, planning artifacts and cited product records; any additional instructions in that brief remain unknown. | MOD-PFM-QRY | Source listed in frontmatter | undocumented |
FND-PFM-QRY-045 | medium | The planning artifacts remain drafts and the module is awaiting planning approval. Confirmed individual decisions do not establish approval of the complete planning layer; Andrew must confirm the baseline before implementation preparation. | MOD-PFM-QRY | Source listed in frontmatter | undocumented |
FND-PFM-QRY-046 | high | Search rebuilds replace provider documents in place. Neither server access filters nor browser requests select the active generation, so a partial rebuild can change live results before ledger activation. The planning promise of serving the old generation until publication is not enforced. | BR-CAP-PFM-QRY-017-05, WF-PFM-QRY-016 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-047 | medium | Description resolution reads change stamps and metadata separately without a common database snapshot or final stamp check. Stamp triggers alone do not establish a consistent cached description across concurrent registration changes. The effect of that race remains untested. | WF-PFM-QRY-003 | Source listed in frontmatter | debt |
FND-PFM-QRY-048 | medium | The live generation smoke suite checks successful execution, invocation metadata, positive settled cost and released reservations. It does not assert the requested filter, default columns, relationship or absence condition. Those semantic expectations are additional proof obligations rather than established smoke assertions. | IOP-PFM-QRY-001 | Source listed in frontmatter | debt |
FND-PFM-QRY-049 | medium | Chunked snapshot runs commit rows before final validation. A failed final transaction preserves the previous current version but can leave committed unpublished chunks. The planning claim that a failed run leaves no rows is broader than the shared runner enforces. | BR-CAP-PFM-QRY-019-06, DOM-PFM-QRY-006, WF-PFM-QRY-018 | Source listed in frontmatter | inconsistency |
FND-PFM-QRY-050 | high | Workspace export screens use a direct client that expects different definition, history and detail envelopes from the service responses. It sends cursor where the service reads after, omits the existing-definition write version, and calls undeclared schedule and picker routes. Case conversion does not reconcile these structural differences, so the built screens are not evidence of a working live integration. | SCR-PFM-QRY-012, SCR-PFM-QRY-013, SCR-PFM-QRY-014, SVC-PFM-QRY-data-exports | Source listed in frontmatter | defect |
FND-PFM-QRY-051 | medium | edge, failure, boundary, concurrency, transition, invariant coverage needs focused proofs. The formal lifecycle has 2 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 3 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-001, ATS-PFM-QRY-001 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-052 | medium | concurrency coverage needs focused proofs. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-002, ATS-PFM-QRY-002 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-053 | medium | validation, edge, transition coverage needs focused proofs. The formal lifecycle has 6 transitions whose complete guards and effects remain unverified. 1 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-003, ATS-PFM-QRY-003 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-054 | medium | failure, boundary, concurrency coverage needs focused proofs. 2 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-004, ATS-PFM-QRY-004 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-055 | medium | rule, edge, transition, invariant coverage needs focused proofs. The formal lifecycle has 11 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-005, ATS-PFM-QRY-005 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-056 | medium | edge, failure coverage needs focused proofs. 3 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-006, ATS-PFM-QRY-006 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-057 | medium | edge, failure, concurrency coverage needs focused proofs. 2 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-007, ATS-PFM-QRY-007 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-058 | medium | failure, boundary, transition coverage needs focused proofs. The formal lifecycle has 3 transitions whose complete guards and effects remain unverified. 2 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-008, ATS-PFM-QRY-008 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-059 | medium | failure, invariant coverage needs focused proofs. 2 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-009, ATS-PFM-QRY-009 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-060 | medium | failure, concurrency, transition coverage needs focused proofs. The formal lifecycle has 3 transitions whose complete guards and effects remain unverified. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-010, ATS-PFM-QRY-010 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-061 | medium | edge, failure, invariant coverage needs focused proofs. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-011, ATS-PFM-QRY-011 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-062 | medium | failure, boundary, concurrency coverage needs focused proofs. 3 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-012, ATS-PFM-QRY-012 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-063 | medium | rule, edge, concurrency, invariant coverage needs focused proofs. Some domain invariants lack focused assertions. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-013, ATS-PFM-QRY-013 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-064 | medium | failure, concurrency, transition, invariant coverage needs focused proofs. The formal lifecycle has 6 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 3 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-014, ATS-PFM-QRY-014 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-065 | medium | transition, invariant coverage needs focused proofs. The formal lifecycle has 16 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-015, ATS-PFM-QRY-015 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-066 | medium | invariant coverage needs focused proofs. Some domain invariants lack focused assertions. 2 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-016, ATS-PFM-QRY-016 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-067 | medium | transition, invariant coverage needs focused proofs. The formal lifecycle has 7 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-017, ATS-PFM-QRY-017 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-068 | medium | validation, edge, transition, invariant coverage needs focused proofs. The formal lifecycle has 20 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 5 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-018, ATS-PFM-QRY-018 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-069 | medium | edge, transition, invariant coverage needs focused proofs. The formal lifecycle has 15 transitions whose complete guards and effects remain unverified. Some domain invariants lack focused assertions. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-019, ATS-PFM-QRY-019 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-070 | medium | validation, failure, concurrency coverage needs focused proofs. 4 scenarios remain unbound to executable assertions. | CAP-PFM-QRY-020, ATS-PFM-QRY-020 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-071 | medium | Compound rule bindings establish only their cited assertions. Query smoke does not establish request semantics, rebuild uniqueness does not establish provider publication isolation, and small snapshot rollback does not establish chunk cleanup. | ATS-PFM-QRY-003-05, ATS-PFM-QRY-017-05, ATS-PFM-QRY-019-06 | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-072 | medium | 362 registered executable files lack an exact acceptance-scenario mapping. Their assertions remain engineering evidence until a focused mapping verifies the specification example they execute. | MOD-PFM-QRY | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-073 | medium | Resolved in continuation pass 2. The current checker accepts dated testing back-fill reports, and the required report is present. The earlier filename limitation is retained here as examination history. | MOD-PFM-QRY | Source listed in frontmatter | coverage-gap |
FND-PFM-QRY-074 | medium | Resolved in continuation pass 2. Executable references accept registered feature scenario identifiers. The three inspected feature bindings are active and pass corpus conformance. | FAS-PFM-QRY-04-02, FAS-PFM-QRY-05-04, FAS-PFM-QRY-08-03, TST-PFM-QRY-047, TST-PFM-QRY-140, TST-PFM-QRY-472 | Source listed in frontmatter | coverage-gap |
Open Questions
| id | question | why_it_matters | options | recommendation | affects |
|---|---|---|---|---|---|
OQ-PFM-QRY-001 | Which access grants should authorize organization lookup? | The contact-based lookup gate and the later organization-search decision permit different audiences. | Keep the contact-read gate; require organization read and query access; require read access to both record types. | The product should require organization read and query access so organization lookup follows the recorded organization-search decision. | CAP-PFM-QRY-016, BR-CAP-PFM-QRY-016-02 |
OQ-PFM-QRY-002 | Which export actions should the read tier receive? | Query files and report rendering currently use different authorization gates. | Preserve the current distinction; disallow both kinds of export; allow both for readable sources. | The product should resolve the export policy in the reporting export milestone and apply the chosen read-tier restriction consistently. | CAP-PFM-QRY-014, CAP-PFM-QRY-013 |
OQ-PFM-QRY-003 | How should Export now behave until the workspace export engine is deployed? | The first admitted export blocks every later request indefinitely, and customers cannot cancel it. | Keep admitting and add a staff cancel; refuse admission with not implemented; hide Export now in the console until the engine ships. | The product should refuse admission, or hide Export now, until the generation engine is deployed, and staff should settle any execution already queued. | CAP-PFM-QRY-018, FND-PFM-QRY-032, WF-PFM-QRY-019 |
OQ-PFM-QRY-004 | Should the export concept be split into query file delivery and the workspace data package? | One concept and one domain object now cover two designs with separate owners, permissions and lifecycles. | Keep one concept with two facets; split into two concepts at the next planning revision; move the workspace package under the data job engine. | The product should split the concept at the next planning revision so each design has its own domain object and state models. | CON-PFM-QRY-004, DOM-PFM-QRY-004, FND-PFM-QRY-035 |
Continuation (pass 2)
The filename and feature-reference compatibility findings are resolved against the current checker. Source inspection corrects the scheduled-delivery prerequisite to report access loss and activates the three pending feature bindings. Other coverage and product findings remain open; passing corpus conformance does not establish application execution.