1 · Baseline, compatibility and evidence limits

WordPress currently recommends PHP8.3+, MariaDB10.11+ or MySQL8.0+ and HTTPS (S01). Its hosting handbook gives more detailed database lifecycle targets (S03). PHP’s official EOL table identifies7.4 as unsupported since November28,2022 (S02). This finding calls for host-supported staging/recovery and compatibility evidence—not a blind runtime switch. Database/runtime requirements must be reconciled with the actual host and current supported-version tables before selection.

Canonical sources retained: every interaction state contains Critical Reasoning, Emotional Acumen, Social Acumen and Physical Health together. PA is analytical/developmental, not an ethical doctrine or human-worth measure. Teams of Three rotation develops articulation, environmental understanding and broader perspective; it does not appoint directors, counters, reviewers or administrators.

2 · Architecture and accountable access

WordPress capabilities are proposed enforcement primitives (S05/S07), not the membership register. Every sensitive operation needs authenticated identity plus resource/entity/community/action authorization. A nonce helps with request context; it is not a substitute for that authorization or replay/idempotency controls (S06). Adopted legal read rights for former members must be resolved in D1 rather than erased by an account-status toggle.

3 · Components: retain, evaluate and reject unsupported assumptions

4 · Complete participation and independent-count workflow

1. Admission and access: an authorized body records actual scoped membership; verify an account separately. Show eligible directory, business access, source/appeal route and historical effective intervals. Payment/contact address/learning role alone does not establish entitlement.
2. Decision and discussion: register V01 exact proposal/version, legal actor, all counting/notice/replacement/deadline rules and electorate snapshot. Connect nomination/business materials and member discussion. No real launch while any required field is unresolved.
3. Independent delivery: the appointed company confirms addresses/identity checks, records invitation/failure/alternative delivery and distinct credentials. Reissues invalidate prior casting ability without erasing history or adding power.
4. Cast and receipt: display exact choice constraints and optional explanation; use the same Unicode rule at every boundary. Preserve accepted exact text, original source and received timestamp. Show a receipt before claiming the event is current/countable; ambiguous MIME/encoding or identity issues go to review rather than invented parsing.
5. Count and member verification: reconcile all raw events to decision-specific current entitlements atomically. Every member can see all named histories, source-linked dispositions, rules and corrections. Secret contact/token details remain outside the ledger. A duplicate receipt is not a new vote; a recording correction is not a changed original choice.
6. Independent correction and report: preserve original and prior interpretation; append authorized correction/recount/appeal with independent evidence and effect. Counter signs a reproducible report; the valid body records result/remaining limits. Unresolved material discrepancy blocks certification.
7. Follow through: publish public result/method; keep full member history and discussion available across leadership/provider changes. Assign actual owner/funds/milestones, record Board named decisions/recusal/dissent and review delivered outcomes.

Email From/header or a logged-in account alone is not adequate eligibility proof. Use the approved member/credential/proxy/assistance checks; common household addresses or networks do not prove duplicate people. Distinguish provider invitation email from an actual email casting route. If a provider offers only web casting, the requested email-counting/casting design still needs an explicit evidenced resolution.

All organizational business remains member-visible: staffing arrangements, compensation decisions, finances, contracts, resource access, teaching/certification performance and conversion. Specific individual information may use an identified scoped handling route with useful business reasons and independent appeal. Moderation cannot quietly rewrite a ballot, cancel a vote, suppress member business access or punish lawful criticism.

5 · Data contracts, credential projection and retention

These are proposed record contracts, not registered endpoints or a running database. Stable IDs link scope, authority and immutable source references. Store UTC effective and recorded timestamps separately. Snapshot prior versions, append corrections, and keep independently held originals/manifests so replay can reproduce the approved projection. The exact reason remains a string; rendering escapes markup without altering its stored words.

A4 remains canonical:12-calendar-month proposed term; independent three-person appeal; start inclusive/expiry exclusive. Case workflow, appeal pending, invoice paid or class attendance never creates active status or extends expiry. Unknown/unissued public IDs return no verified credential, without implying dishonesty or revealing private case facts. Public lookup uses the exact allowlist above, not public name/applicant search.

Do not reuse educational evidence periods as voting, corporate, payroll, accounting or agency schedules. D1 must complete those actual duties; case/vote open disputes preserve specifically scoped sources. Periodic hold review and documented release avoid an indefinite blanket archive. Backup/replica disposal and reintroduced data after restore need coordinated approved handling. No actual deletion or retention clock is enabled by this plan.

6 · Mail, payments, recovery and change operations

Reliable notices and receipts

Use a durable outbox and purpose/version/recipient idempotency key. Record queued, provider-accepted, delivered, accessed, failed and alternative-route evidence separately. WordPress wp_mail success is not proof the recipient received the message (S08). Reconcile ambiguous sends before retry; preserve original deadline/access-failure evidence. Use synthetic destinations in staging and disable outward delivery; real notices require actual authority and a valid service.

Payment integration without purchased authority

Validate actual gateway and webhook payload signatures, amount/currency/entity/order/reference and event age/state; deduplicate delivery IDs and reconcile current gateway/order evidence before fulfillment. Official WooCommerce v1 webhook reference describes HMAC-SHA256 and delivery IDs (S16); installed/gateway behavior is still unverified. Pending/on-hold are not completed payment; a manual refund status alone need not mean funds were returned (S15). Payment/waiver/refund events never directly change membership, votes or credential outcome. Licensing rights and authorized prices/owners remain B2/D1/D3 gates; no card secrets belong in member histories.

Backup and restoration runbook

1. Inventory database,plugins,themes,uploads,config/host routing,external event/case storage,counter originals and mail/payment reconciliation state. Identify exclusions and restore dependencies.
2. Confirm an independently accessible encrypted copy and actual responsible/deputy custody; secrets are referenced from controlled storage, not printed in RP. Updraft vendor docs do not establish this site’s remote coverage (S09/S10).
3. Before migration, retain current revisions and a verified recoverable snapshot. Restore into isolated authorized staging with outbound mail/payment disabled; compare object counts/hashes, page/menu/record histories and critical flows.
4. Measure actual recovery and loss boundaries. Proposed public-content target:24-hour recovery-point window and8-hour recovery-time window. Acknowledged ballot/correction/credential events require durable independent copies and reconciliation so no acknowledged event is silently lost; do not advertise zero-loss recovery until demonstrated.
5. If rollback needed, stop affected writes/verification, preserve new events after the snapshot, restore only authorized scope, replay/reconcile them and verify public/member projections. Never overwrite post-backup valid votes with an older snapshot.
6. Record restore operator/witness,backup/version,sources,elapsed time,missing records,side effects,exceptions and successful checks. Resume only with a documented bounded decision.

This is infrastructure recovery planning. The canceled website-wide Word/ZIP export remains canceled; no such export or actual site backup was created. No staging/restore/production mutation was performed.

Incidents, updates and deputies

Propose weekly delivery/error/access/discrepancy queue review; monthly dependency/permissions/storage checks; quarterly isolated recovery rehearsal; before each election, review source/configuration/counter independence and capacity. For material ballot/history mismatch, stop certification, preserve originals, route independent review and notify through valid authority; do not alter deadline or conceal unfavorable records. For a specific individual-data leak, restrict the affected exposure and preserve incident evidence while retaining lawful business access; actual notification duties require D1’s jurisdiction basis.

Record change/version/dependency diff,owner/approver,staging evidence,backup/rollback plan and success/exception result. Deploy using supported WPVibe operations and fresh exact anchors for content; no raw SQL/security bypass. Existing copy-protector/rights conflict is D3/H3 review work, not permission to disable it. No subscription, account/access expansion, host migration or installed-component change occurred.

7 · Capacity, funding and accountable owners

Proposed initial planning workload:100verified members, two independent decision cycles/year and modest moderated discussion. This is an evaluation scenario, not actual membership or a throughput guarantee. Assign an accountable owner and deputy for membership/access, system/recovery, independent count, moderation/appeal, credential/case custody,finance and rights. One person holding multiple administrative roles must not decide their own ballot discrepancy, compensation or appeal. Independent duties need real funded capacity.

Actual providers/hosting/storage/security/accessibility/payment charges and reviewer wages must be quoted. These allowances are editorial assumptions; no funds approved or spent. Legal/accounting review, formation, products/teaching, reviewer/three-person appeal casework and taxes are outside this scenario. Reconcile B1’s overall budget and the C3 per-election illustration rather than adding duplicate line items; a new illustration does not silently replace either earlier source. Variable demand and review backlogs need separate funded expansion/stop rules.

8 · Acceptance contract and reproducible scenarios

All24 system acceptance scenarios below are NOT_RUN. No site/component/hosting/provider/permission/recovery/payment/mail/end-to-end capability is reported as passing. The companion JSON supplies each scenario’s setup,expected outcome,requirement links,unassigned owner and empty evidence reference. Synthetic testing is a future implementation contract, not an actual vote or independent verification result.

Local preparation checks can establish intact source linkage, valid internal references, canonical A4 field/retention preservation and arithmetic; they do not pass these end-to-end scenarios. H3 owns the broader display/accessibility/copy/print audit; C4 implements actual forum/voting membership flows after its dependencies and real launch gates are satisfied.

9 · Deployment gates and publication queue

Publish this technical planning resource in existing member-participation2547 and a compact Operations Manual2626 interface only after fresh raw/anchor/rights checks. Preserve original#forum/#membership and O-06 clauses, source text, C3 compact script, navigation and all existing menus. Verify exact intended insertions, reciprocal links and scoped display; a planning publication remains distinct from an enabled service.

H4 remainsIN_PROGRESS: technical resources prepared, no current stack/restore/authorization/end-to-end evidence or website publication. D1 remainsIN_PROGRESS with California public-benefit/statutory-member model selected; its review draft stays queued. C4 remainsQUEUED and no live participation component is activated. The conditional continuation watcher remains unconfigured until required successful website preflight, as recorded in RP.

Next action: recover the latest RP and artifacts; after the indicated access window, one harmless site check, current target/inventory/backup reads, then eligible draft publication and compatibility/recovery planning. Obtain actual host/staging and lawful scope/rights/counter/funding information before any consequential deployment. Current-site evidence, actual provider configuration and all24 acceptance outcomes remain open.

10 · Sources and provenance

External sources checked October8,2026. Primary technical documentation and vendor feature claims support only the bounded context below. No actual provider security assurance, service pricing, installed compatibility or site-operation claim follows from them.

Internal current sources: RP31 at start; index11/register13; C3 specification; canonical A4 continuing-review and status-register specification; curriculumv0.3. The canonical A4 JSON’s public allowlist,12-month term,case separation and differentiated proposed retention are imported unchanged. Existing alternative A4 drafts do not supersede them. All diagrams/contracts/timing/capacity/budget/component-fit decisions and acceptance scenarios here are editorial proposals.

Historical site inventory comes from RP and prior successful site_info; no fresh site request made against the known daily block. No current restored backup, staging instance, technical account, configured provider, gateway settlement, real membership record or independent verifier was observed.