Remaining questions — updated 3 October 2026¶

Current DP6 correction: personal Include governs within-stage steps; cross-stage routing is configurable. DP7 confirms Collective Include required as cross-stage default; advanced own-Include option allowed. Strict within-stage details remain proposed. Older blanket cross-stage DP1 wording below is historical/superseded.

This inventory reconciles the original v10 decision register against the latest owner ledger, handover and comparison. Original Open labels are historical evidence, not a reason to ask settled questions again. Recommendations below are proposals, not approval. No implementation or prototype validation is claimed here.

The first usable infrastructure slice is M1 ordinary annotation versioning under the common contract; the shared-form review-step journey builds on it, including version, provenance, eligibility and publication correctness. Questions for reconciliation, schemas, analytics and completed-stage lifecycle belong to their respective delivery slices. Do not make those later decisions prerequisites for shipping the first usable slice.

Remaining concrete proposal approvals¶

Major product decisions are covered. These are reviewable execution/setting recommendations, not a request to repeat the original product discussion. P10 single outcome-measure direction is settled. P9 planning is now authorized, implementation/migration is not.

ID / source	Concrete approval item	Confirmed boundary	Reviewable proposal
P9 · MIG1 · Plan ready	Mapping/adoption, scoped cutover and recovery approach	Planning authorized; no execution; legacy evidence and histories preserved	Migration plan: dry-run legacy adapter, reviewed manifest, staged copy, write fence, rollback boundary
P11 · LC1 · Policy settled, mechanics proposed	Exact protected-change/admin-confirmation flow and manual reopen/draft routing	No applicable unresolved drafts/corrections at auto completion; confirm before change; then auto/manual mode behavior	Settings proposal: per-affected-stage approved change, source recheck, explicit manual reopen
P12 · PM2 · Matrix ready	Separate action labels/defaults and bounded delegation mechanics	Owner grants administration to project group; transfer owner-only; use differs from administration	Matrix and RBAC research; bundle names implementer discretion
P14 · UA1 · Narrow settings/method review	Gold completeness scope/default; missing/Unknown comparison and denominator contract	Required candidates answered; optional blanks reconciler decides; blank not N/A; AG3 equality/version flags settled	Settings proposal: project Follow requiredness default, form inherit/override; separately approve missing statistical contract

See the implementation plan for a coherent first slice and complete M0–M8 sequence. No broad reconfirmation or new planning session is needed.

PRISMA integration amendment/coverage review¶

Prior package approval request is superseded. DP7 cross-stage default is confirmed (Collective Include required, advanced own-Include option). Optional strict within-stage policy remains proposed. Review explicit A–F amendments in the PRISMA comparison alongside the revised sequence: protocol entry versus personal access, report identity/count units, consistent earliest-source column rule, reviewed-dedup identity handling, pending reason coverage and recoverable as-of manifest. These are concrete source conflicts/engineering contracts, not reopened broad choices. Follow existing FEAT-011 affected-spec/phase/checklist change policy before claiming complete output.

Engineering contracts to propose, not repeat as owner questions¶

ID / sources	Concrete work to resolve	Fixed boundary / current baseline
E1 · FV1–FV4, PV2	Specify per-session-category application of existing requireReanswer/autoUpdate/doNothing, affected identities, pinned bindings, and policy revisions after work has already been performed.	Admin confirms publish impact over all prior versions; treatment/counting is admin-controlled. FV4 permits revising an unnecessary requirement with new history. Original versions/work remain immutable.
E2 · SF3/SF5, SL1–SL3	Specify answer identity for ancestors/repeated entities/branches, legacy duplicate-conflict detection, stale-base writes, and atomic new incomplete version creation on Fix.	Own prior answers and all ancestors are visible across forms/stages. Fix explicitly creates a current incomplete session, preserving old Complete history. Autosave is not confirmation; no automatic adoption. SF6 confirms current Complete still counts despite the warning alone; recorded action/policy generating current incomplete work removes qualification. Implement triggers explicitly; no automatic invalidation from every shared-answer change.
E3 · PS1–PS3	Define relevant materialized usage families, protected publication boundary, fencing/catch-up/targeted refresh, affected-record enumeration and safe pause recovery.	Statistics must be current at publish; missing/stale is not zero; admin choice gate is required. Aggregate counts do not identify every record to transition.
E4 · QY1–QY7	Specify concurrent resolution, snapshot replacement, shared study/form reconciliation task claims/locking, queue allocation and private notification delivery.	Pending gold stays effective; grouped version work has individual concerns; children valid before replacement. Permitted audited query self-review and optional rejection explanation are settled. QY8 addressed concerns close individually with resolving-version history and notification; uncertain satisfaction needs manual review. QY9 preserves unsatisfied concerns open on original version and flags assigned reviewer to check current applicability; generic policy settled, concurrency remains.
E5 · DP1, OD2/OD16	Specify cross-stage dependency propagation, profile-version reassessment and partial combined-step reservations/admission.	DP6: own Include permits within-stage steps; cross-stage routing configurable, collective default confirmed by DP7; collective Exclude veto and EW1 saved-work policy; different profiles not merged; no fabricated votes or duplicate form contributions.
E6 · RA1–RA5, AG1, BL1	Map grants to existing authority; define assignment start/release/reacquire races, additional-review idempotency and blinded source aliases.	Assigned unstarted work only expires; started release retains work; additional review needs its own capability; statistics view does not imply candidate access.
E7 · MG1, SF4/RE3	Propose normalized match scoring, missing-feature behavior, ties and multi-reviewer groups; specify correction/reference remapping.	Suggestions required from labels/answers; top-down/parent context is proposed v10 design. Exact weights/thresholds unapproved; no sample-size heuristic/AI requirement. All qualifying candidates participate.
E8 · GS1, RD13, EX1	Specify immutable snapshot identifiers/current selection and full historical reconstruction, coherent answer/definition/permission cutoffs and export manifests.	EX2 includes available recoverable historical/pre-migration data without arbitrary date/retention cutoff; no fabricated legacy snapshots. Current downloads default; historical/as-of downloads required. Open QM groundwork reserves historical modes but only supports CurrentState; merged plans are not proof of implementation.
E9 · AG2, VS2, RD14	Propose an explicit statistical method and denominators for multi-reviewer, entity, missing-state and version-compatible data.	Identical multi-select sets agree; option overlap is separate. Independent/informed assessments stay distinguishable. AG3 confirms explicit N/A equality and flagged compatible-question-version comparisons; no auto incompatible comparison. UA1 optional-blank reconciliation is settled; exact gold completeness and missing-state/denominator proposals remain; no selected κ formula or majority-gold rule.
E10 · OD13	Define evidence-based legacy session/version mapping, dry-run invariants, recovery and rollback.	Never fabricate historical versions, source provenance or semantic compatibility. Preserve existing work; reconcile legacy conflicts visibly.
E11 · DP5 / RC9	Specify configuration handling and missing-input behavior when reason collection is Off but reason reconciliation is On.	Profile toggle is confirmed: enabled applicable reasons follow profile rules; disabled no reason-reconciliation requirement. No hard dependency, forced setting change or mandatory blocking gate has been approved. Preserve reasons/history and independent decision resolution; do not fabricate absent reasons.
E12 · OC1	Specify legacy-compatible/event-count schemas and project-customization field roles, types, meaning, requiredness, validation and exports.	First-release catalogue/customization is confirmed. Numerator/denominator, range, CI, standard error and variation are examples; no mandatory third bundle, no variation=variance/SD or approved formulas. Retain versioned project ownership; MIG1 authorizes migration planning, not execution.
E13 · RX2 / OD18	Map stage lifecycle actions to existing authority and specify readiness/new-study events, idempotency/concurrency and interactions with session-version qualifications.	Auto/manual completion and auto reopening when new studies arrive are recovered design; runtime watchers/status-event persistence not verified by toggle messages. LC1 settles unresolved-work and pre-change confirmation; exact draft/approval routing proposed; preserve historical completion and pins, no speculative new reopening permission.
E14 · TC1	Validate existing entity-type catalogue, legacy name/ID mappings and feature-required system-type dependencies.	Existing-type templates and conditional extraction/export system types are confirmed; no universal every-project requirement or invented exhaustive catalogue. Prototype demonstrates templates/dependency design, not full runtime mapping.

UI choices and prototype validation still outstanding¶

ID / sources	Concrete design or validation question	Fixed baseline / recommendation
U1 · RD17, SF4/RE3	Can the stage reconciliation workspace demonstrate decision-agreed/supporting-answer-pending work and scale to three/four or more candidates while keeping the form usable?	4a+3a remains proposed, not a verified final choice. Validate compact candidate selectors/lists, access to every candidate, stable aliases, matching groups and outcome comparisons; avoid two-slot assumptions.
U2 · RC6	Should reviewers have a per-step Skip/handoff action in addition to moving to the next study, and how is its scope made clear?	Navigation Skip casts no Exclude and records no completion. Preserve familiar action-bar behavior.
U3 · RC8	Where should shared study-population context sit in the familiar reviewer UI?	Population ownership/inheritance is settled; a header chip is current prototype choice, not a new per-location population question. Test against normal SyRF tabs/question numbering.
U4 · RE2, SF5	Validate obvious autofill marks, actual control exposure warning/routes and affected-session Fix navigation.	Complete anyway is confirmed; tab opening/offscreen rendering does not establish exposure. Fix creates incomplete session and opens its own form; no per-field confirmation/read-proof gate.
U5 · PS1–PS3 / OD5	How should publication-pause/retry and dependency-change messages preserve work without revealing blinded votes?	Visible queued exact-version retry and active-reviewer warnings are recommendations only. Require clear local prototype behavior; no routine disruptive messages or candidate leakage.
U6 · FV1–FV4	Does publication/requirement-revision UI clearly show completed, saved incomplete and draft-only impact and applicable existing choices?	Reuse recovered choices and admin confirmation, not a new universal count/does-not-count decision; no unapproved auto-migration.

Settled items excluded from the question list¶

P15/X2/TC1: templates default to existing legacy entity types; system cohorts/outcome measures/ experiments are required when relevant form extraction/export is used, not universally. Exact catalogue and legacy alias/dependency verification are engineering, not generic promotion policy.
P14 N/A/version portion/AG3: explicit N/A equality and flagged compatible-question-version comparison settled. Only literal missing-state/denominator treatment remains P14. EX2 historical availability includes recoverable pre-migration data without arbitrary cutoff; no fabricated history.
P13/QY9: unsatisfied concerns remain open against original target/version and are flagged for assigned-reviewer current-applicability check. No automatic retarget/delete/closure from replacement alone. QY8 clearly addressed concerns can still close individually.
P12 groups/scoped-grant architecture/PM1: configurable project groups and membership/grants UI are confirmed. Only explicit capability granularity/scope/admin-default matrix remains P12; owning a capability does not grant administration rights and ownership transfer is excluded.
P11 automatic/manual/new-study portion/OD18/RX2: recovered from original stage prototype; automatic completion and new-study reopening, manual mode, frozen completed configuration, preserved drafts/pins and status history are documented. LC1 settles unresolved-work and pre-change admin confirmation; exact approval/draft/concurrency flow is now a concrete proposal.
P10 placement/OD11/OC2: greater-is-worse metadata belongs to the versioned outcome measure. ODIR1 settles P10: one direction per measure, no cohort/population override; distinct meanings require separate measures.
P8/OD9/OC1: first schema release includes legacy-compatible, event-count and project creation/customization. Numerator/denominator, range, confidence interval, standard error and variation are configurable-field examples, not a mandatory fixed bundle. P9 migration plan is now supplied under MIG1 for approval; execution is not authorized. Event-count/field specifications are domain/engineering work.
P7/RD6/RE5: actual free-text answers use exact compatible candidate-text agreement for prefill; otherwise reconciler supplies/chooses response. No fuzzy/semantic/normalized or synthesized prefill; candidate authors/provenance and existing gold/drafts retained. Contextual notes and screening supporting-text rules remain distinct. RE2 exposure warning still applies.
P6/RD4/RE4: one study/form reconciliation task shared across stages using the form, pinning exact form/candidate versions. Completion satisfies compatible form requirements, not unrelated profile/stage work; shared question gold is not duplicated. Claims/locking/compatibility are engineering details, not a reopened task-unit choice.
P5/RC9/DP5: profile exclusion-reason reconciliation On/Off is confirmed. Enabled applies configured reason rules; disabled removes that requirement while preserving candidate reasons and independent decision resolution. No collection-Off hard gate or forced setting change approved; precise combination handling is E11.
P4/X3/RX1: recovered profile-owned decision-versus-supporting-answer agreement/resolution contract. Two Excludes with configured reason disagreement still require reason resolution; form reconciliation remains separate. Required supporting-answer work appears in stage reconciliation for a stage using that profile, presenting shared profile authority without duplicate stage-owned answers. Supplied prototype decision-count logic does not demonstrate the full contract; integration/validation and RE4 technical claim/locking mechanics remain.
P3/OD7/DP4: screening questions/configuration belong to the profile; templates supply copies, not shared live configuration. Same-profile stages share profile-scoped answers; separate profiles do not. Ordinary study-fact sharing and editor reuse remain unchanged.
P2/OD8/DP3: proposed rule-derived individual screening decision is confirmed with relevant answers on explicit submission. Field changes/autosave cast no vote; no separate per-answer confirmation; show triggering criteria and own answers with pinned versions, respecting blinding. Collective agreement and gold remain distinct.
P1/OD3/DP2: own review history opens the study for deliberate correction of personal Exclude to Include and a new immutable submission if reviewing remains possible. Access, admission and permissions still apply; accepted reconciled decisions use queries. Original Exclude history retained, eligibility re-evaluated, no automatic re-invitation.
OD1: DP1 personal Include across configured stages with collective Exclude veto.
OD4: SF4/RE3 all qualifying compatible effective candidates beyond the minimum target, and more-than-two-reviewer UI. Eligibility/concurrency mechanics are separate.
OD14/OD19/OD20: SF1–SF3 shared form/session/target, compatible answer reuse and SL1–SL3 current explicit Save/Complete lifecycle. SF5 specifies ancestor visibility, older-session warnings and optional Fix creating a new incomplete session; no stage-wide auto-incompletion.
OD15: PV1/PV2 versioned settings and exact revision source/exposure provenance.
OD17: GS1 immutable accepted snapshots and EX1 historical/date-specific download requirement; reconstruction mechanics remain E8, not whether reproducibility is wanted.
RD1: MG1 match suggestions required; numerical scoring is E7.
RD2/RD5: RE2 final form acceptance, obvious autofill, unseen-control warning and Complete anyway; no per-field confirmation gate or agreement-to-gold auto-promotion.
RD6 contextual notes: NT1 original notes retained and copying keeps original author/source; actual free-text answer contract is settled under RE5, not a note-synthesis requirement.
RD7: BL1 stage-owned consistent identity blinding.
RD9/RD10/RD11: RA assignment/expiry/release and separate additional-review capability; RE1 reconciliation explanations optional, including disagreement with every candidate.
RD12: FV4 revisable unnecessary update requirement, not arbitrary semantic compatibility.
P16/SF6: current Complete retains completion qualification despite an outdated-answer warning alone; reviewer/admin action under recorded policy creating current incomplete work removes it until a valid Complete. No universal auto-invalidation trigger is approved.
QY8: clearly addressed concerns close individually against the resolving accepted version with author notification; uncertain satisfaction needs manual review. QY9 settles unsatisfied concerns too: keep original version/open concern and flag assigned reviewer against current answer, without silent retargeting; concurrency remains engineering.
RD14 multiple-selection equality: AG2 exact selected sets, separate overlap. Method is E9.
RD15/RD16: existing matrix/dialog/spreadsheet/graph pattern and planned outcome reconciliation.
RD18 agreement metrics: AG1 separate grantable statistics-view capability without candidate answer access or implicit Reconcile grant; map remaining action permissions under E6/P12.
RC10: re-evaluate submitted corrections under current rules; manual work only when still required, preserve dependencies/history. Do not reopen it as universal manual re-review.
OD12: advanced semantic mapping and optional breadth beyond confirmed OC1 project-schema creation/customization are progressive enhancement. TC1 separately settles existing-type template defaults and conditional feature-required types.

This inventory does not treat designer recommendations as owner approval. The unchanged source v10 register/prototype remains historical evidence; the owner overlay governs conflicts.

Latest confirmed direction and concrete approval proposals — 3 October 2026¶

This section supersedes earlier deferred/open wording for P9–P14 where stated; original source prototype and historical discussion are retained, not rewritten as implemented behavior.

LC1 / P11: automatic completion requires no unresolved applicable work, including drafts and outstanding corrections. Alert project admin and obtain confirmation before admitting a change that would reopen a Completed stage. Commit approved change then auto transition in automatic mode; manual mode requires explicit reopen/switch-off. Preserve new-study auto reopening under this gate, current Complete counting until actual incomplete-version action, autosave/draft distinction and history. Precise approval/concurrency/draft routing is proposed, not a newly approved permission or spontaneous reopening.
UA1 / P14: required applicable questions cannot be omitted in completed candidates; optional unanswered questions can be decided by the reconciler. Blank is not N/A. Configurable all-applicable-gold completeness was suggested; project/form scope/default and statistical missing/Unknown comparisons/denominators remain approval proposals. AG3 N/A/version and EX2 available-history decisions stay settled; Complete anyway never waives answer validation.
PM2 / P12: project owner can assign permission administration to a membership group; authorized members administer/delegate within approved scope. This deliberately extends currently owner-only AssignPermissions. Ownership transfer remains owner-only. Proposed owner-reserved delegation-envelope administration/non-recursive delegation boundaries are explicit recommendations. Possessing a grant never means administering it. Group template names/bundles are implementer discretion after complete action inventory, not owner blockers.
ODIR1 / P10: one versioned outcome-measure direction across cohorts in a paper/population; no context override. Genuinely different meanings require separate measures. Earlier open override proposal is superseded; retained conflicting legacy values require reviewed mapping.
MIG1 / P9: drafting outcome migration/adoption plan is now authorized, superseding deferred planning status. Execution, activation and live migration remain unauthorized.
IP1: concrete implementation planning authorized, not runtime code. Major product choices are covered; review remaining exact proposals before implementation instead of reopening them.

Reviewable standalone documents:

All are planning deliverables. Approval choices are marked; no default/grant, data conversion, statistical formula, production lifecycle behavior or source-prototype update is claimed.

PRISMA integration review required before implementation approval — 3 October 2026¶

Chris requested existing PRISMA plans be integrated. The prior package approval request is superseded. The PRISMA compatibility comparison identifies existing binding source constraints, verified local gaps and current PR overlaps; the revised implementation plan, permission matrix and migration plan now include phase dependencies, unit/authority boundaries and regression gates directly. Original Approved source specs are not silently changed. Explicit A–F recommendations cover personal admission vs collective authority, report/Citation multiplicity, conflicting source-column queries, reviewed dedup, pending reason coverage and coherent historical report provenance. Existing product decisions remain preserved. No runtime/migration/grant changes are authorized.

DP6 — current cross-stage correction (supersedes DP1 cross-stage extension)¶

Chris, 3 October 2026, during PRISMA integration: personal Include with collective Exclude veto applies to steps within the same stage. Between stages, route availability should be configurable. Proposed choices are Collective Include required versus own Include sufficient; collective Exclude veto, permissions/allocation and independent gating remain. DP7 confirms default Collective Include required, with advanced own-Include option; collective Exclude veto retained. Record this as a change of direction, not a denial of earlier DP1 confirmation. Older blanket personal-Include cross-stage language in historical sections is superseded. Keep within-stage personal work, cross-stage routing and PRISMA collective report authority separate. Cross-stage default is settled under DP7. Review strict within-stage proposal and PRISMA amendments before implementation approval.

DP7 / PR1 — confirmed cross-stage default and collective reporting¶

Chris confirms cross-stage default waits for collective Include; advanced own-Include access is allowed with collective Exclude veto. Within-stage default remains own Include. Optional strict within-stage collective gate needs design; its exact inheritance/override/unfinished-work handling is proposed in the access-policy document. PRISMA reports collective authoritative outcome: Excluded stays Excluded even when extra review/ annotation work was completed under earlier access. Preserve that work and provenance. This settles DP6's pending default, superseding provisional package wording; no runtime approval follows.

SET1 — requested optional setup and template scope¶

Chris requests default screening-profile templates, an encouraged editable initial annotation form, ordinary annotation question-library selection and optional guided preclinical admin setup. Exact contents/steps remain proposals. The setup plan uses existing category editor/import/version/publication machinery and PRISMA dependency contracts; profile templates copy into profile-owned eligibility definitions, never shared ordinary facts. The implementation sequence now includes these deliverables; no runtime implementation implied.

SET2 — existing wizard replacement correction¶

Chris clarifies guided setup replaces the existing CreateProjectWizard/ProjectSetup workflow, not an additional parallel wizard. Current entry/component/checklist inspected; the setup plan now maps retained fields/routes/commands, feature gates and explicit retirement/parity checks. Exact robust replacement UX/content remains proposed; no runtime changes authorized.

OPS1 — existing operations and overview/settings integration¶

Chris requires existing/ongoing materialized statistics, allocation, active-work tracking and batching to be integrated, plus project/stage overviews and project/stage/step settings for shared forms/steps. Operational integration map records inspected source contracts/active PRs, amendments, parallel lanes and join gates. Existing programmes/PRs remain owned; no changes, activation, arbitrary new metrics or extra agents authorized.