Questions, answered.

Campaign fundraising and organizing teams that need separate workspaces for their records. It is in development; public distribution is not yet ready.

Local acceptance evidence covers workspace identity, memberships and sessions, profile/contact records, reviewed imports, and saved filters with list snapshots. This is synthetic local testing, not full-product release qualification.

Workspace IDs and server-enforced membership controls scope access. New workspace identities cannot select legacy donor records automatically. Role changes and session revocation have dedicated local checks.

The current reviewed import workflow inspects CSV, TSV and XLSX files, maps columns, and separates accepted, duplicate, invalid and ambiguous rows for explicit review. Legacy workbook support is not a promise of complete migration fidelity.

No. Imported records do not establish consent or verified contact status. Review source rights and contact permissions separately.

Merge and unmerge previews preserve source histories in the local implementation. The broader workflow remains partial while allocation and consent conflict checks are completed.

Saved filters and immutable list snapshots have local acceptance evidence. This does not establish a complete collaborative phonebank, dialing or reminder workflow.

Local workflows include scoped archives and call-sheet exports. Identity, profile and import archives have different contents. A workflow archive is not a complete portable backup of every record, credential or integration.

The relevant workspace identity and current local authority must match. Restore validation and interruption checks use synthetic records. Complete clean-machine recovery, upgrades and realistic production backups remain release gates.

No. Local storage and optional external processing are separate. AI providers, research sources, telephony or synchronization may require network access and configuration. Provider readiness is not proof of a completed external operation.

Research is designed to keep AI optional and preserve fallback behavior. A configured provider or availability indicator does not guarantee a live response.

Contribution records and rule lookups are not payment processing or filing submission. These complete workflows remain unfinished; the current build should not be represented as providing them.

A supported public installer, clean-install qualification and distribution instructions are not available yet. No download is offered on this page.

Pricing and the public distribution license remain unresolved. No price, subscription or open-source license commitment is made here.

The portfolio contact is hello@patchworkmd.dev. A dedicated support policy and response commitment have not been established.

There is no confirmed public launch date. Remaining workflows, accessibility, scale, clean installation and distribution must pass their release reviews first.