Furries PH Docs
Dashboard

Updates

Platform Updates

Public-facing release notes for meaningful changes across Furries PH operational systems.

First created Last updated

Showing release notes 1061-1070 of 1463
2026-08-1306:37

EPS Designed UI and Persistent SPA Certification

Repositories: partners.furries.ph, docs.furries.ph

Status: Preview; local visual, interaction, and resilience certification passed

What’s Changed

  • The EPS portfolio, overview, My Work, Schedule, Requirements, Departments, Meetings, Files, Notifications, Risks, Gates & Handoff, Event Configuration, and Settings surfaces are registered in the persistent dashboard SPA shell.
  • Seamless sidebar navigation now remounts the correct EPS scene and every route’s designed primary dialog without replacing the dashboard document.
  • Visual QA confirms the full route and modal atlas, including New Department, membership/RACI/capacity, requirement approvals, meeting notes/minutes, Sanity-only evidence, notification destinations, controls, gate decisions, EMS changes, and project settings.

Validation

  • The 144-page static build and Astro diagnostics pass with zero errors.
  • EPS contracts and representative-volume resilience certificates pass, including 10,000 work items, 20,000 requirements, 50,000 activity records, reminder replay, and atomic 500-row import identity.
  • The browser certificate passes all 13 planning routes, twelve persistent-SPA route transitions, each event-scoped primary dialog after SPA remount, all representative secondary workflows, and desktop/mobile Department states with zero runtime errors.

Next Step

Controlled migration application, secret provisioning, deployment, and hosted non-production canary evidence remain operator-owned rollout actions.

2026-08-1306:37

AMS Design Fidelity and SPA Hydration Certification

Repositories: partners.furries.ph, docs.furries.ph

Status: Historical Preview evidence; superseded by the corrective AMS update above

What’s Changed

  • Owned and loaned asset registers now include the designed KPI strip and operational attention queue; checkout, transit, audit, maintenance, and logistics routes include their designed exception rail.
  • Settings now preserves the approved three-part desktop hierarchy—master-data tabs, register, and attention queue—without collapsing workflow actions into the narrow navigation column.
  • Import, exception filtering, Settings tabs, and governed configuration export are functional in direct loads and persistent-SPA navigation.
  • SPA scene hydration now updates the added KPI and attention layers after route transitions instead of leaving loading placeholders behind.

Validation

  • The 144-page static build and Astro diagnostics pass with zero errors.
  • AMS database, no-oversell concurrency, recovery, policy, and SPA route-list certificates pass.
  • The then-current authenticated browser smoke certificate passed 56 checks across ten routes and captured 75 route, modal, scanner, and responsive states. A later board-by-board corrective audit found material density and workflow-depth gaps; use the newer 58-check/77-capture manifest only as current fixture regression evidence, not visual release sign-off.
2026-08-1306:37

EPS Authorization and Volume Certification

Repositories: partners.furries.ph, partners-api, rego.furries.ph, docs.furries.ph

Status: Preview; local implementation and certification complete, controlled hosted rollout pending

What’s Changed

  • EPS now requires explicit project membership or partner/platform administration, then applies role capabilities, department scope, parent-resource access, and confidential/restricted classification checks throughout workspace reads and mutations.
  • Calendar exports, meetings, requirements, risks, gates, notifications, audit, handoffs, canonical EMS proposals, and protected file downloads expose only the data granted to the current Planning role. Protected files also enforce configured role and department policies before authenticated proxy download; raw Sanity URLs remain prohibited.
  • Representative resilience certification now covers 10,000 work items, 20,000 requirements, 50,000 activity records, 300 participants, and 20 departments. Rego diagnostics, build, canonical EPS publication boundaries, and desktop/mobile Event Shop browser flows also pass.
  • EPS publishes a machine-readable OpenAPI 3.1 description using JSON Schema 2020-12, and dependency-date application, baseline creation, and stage-gate decisions now commit through atomic database functions.

Next Step

Operators do not need to change local planning data. The remaining release work is controlled migration application, Worker secret provisioning, deployment, and hosted linked-event/upload/notification/publication canary evidence.

2026-08-1306:37

Finance Management Design 2 Workspace

Repositories: partners.furries.ph, partners-api, docs.furries.ph

Status: Preview; locally certified and ready for hosted canary review

What’s Changed

  • All 14 partner Finance Management routes now use the approved dense operational layout with AMS-style nested navigation, compact KPI strips, portfolio and workflow tables, event-aware filters, detail rails, audit context, and predictable centered dialogs.
  • The Finance overview now follows the approved five-metric, cross-event ledger, selected-event cash bridge, latest-outflow, commitment-health, and audit-activity hierarchy. Duplicate page headings and unresolved runtime icon placeholders were removed.
  • Finance tables and detail panels now respond to the available dashboard shell width, preventing clipped columns and document-level horizontal overflow on narrower desktop windows while retaining dense desktop layouts.
  • Partner-wide and event-specific outflows expose accountable checkout, maker-checker state, evidence and notification context, while payables, receivables, expenses, budgets, close, reconciliation, automation, integrations, and settings share one consistent workspace language.
  • Every Finance route is registered in the persistent dashboard SPA shell. Rapid route switching now safely cancels stale overview rendering, and Astro/Vite module transforms remain intact during SPA script remounts.
  • Linked-project current-history inspection corrected a Finance pgcrypto schema-resolution defect and now verifies required migrations, privileged-function grants, the deployed Finance schema, and a forced-rollback synthetic partner/journal mutation without retaining finance records.

Impact

Finance teams can move between partner-wide books and event detail without page reloads, use the same navigation and control patterns throughout, and inspect more financial context without opening separate pages.

Validation

  • Astro diagnostics pass with 0 errors; the 144-page static build passes.
  • The complete local Finance certificate passes database/accounting invariants, 29 independent calculations, mutation sensitivity, 16-actor concurrency, one-million-line volume, logical restore, accessibility, 54 API contracts, Telegram/Discord provider contracts, security hardening, and SPA-manifest coverage.
  • Current in-app-browser evidence covers all 14 routes and 15 representative modal entry points with no console errors. Approved-source and implementation comparisons are retained in the Finance certification evidence directory.
  • A fresh 1120 × 912 visual pass confirms every Finance route stays within the viewport. The outflow modal measured centered to the viewport within the scrollbar offset, and the corrected overview comparison is retained as overview-approved-vs-implementation-final-v2.png.
2026-08-1306:37

Event Planning System Preview Workspace

Repositories: partners.furries.ph, partners-api, rego.furries.ph, docs.furries.ph

Status: Preview; ready for migration and deployment review

What’s Changed

  • The new Event Planning System (EPS) adds a complete pre-event workspace for schedules, requirements, departments, meetings, controlled files, reminders, risks, readiness gates, event configuration, and project settings.
  • Schedule records now share real Gantt, calendar, table, board, workload, and baseline views. Every visual has a keyboard-accessible table and focused edit dialog.
  • Schedule now also includes month/week/agenda calendar modes, dependency and critical-path Gantt context, zoom, approved-baseline overlays, hierarchy/WBS, accessible signed-day rescheduling, scenarios, and reusable personal/team saved views.
  • Department workflows include creation, effective membership, RACI, and capacity designs; meeting workflows include externally hosted calls, ordered agendas, versioned minutes, decisions, and canonical follow-up actions.
  • Department/role requirement templates assign idempotent user obligations to current and later joiners. Their due-date reminders are created in the same transaction, so a successful assignment cannot be left without its notification schedule. Requirements support draft/final versions and withdrawal before review; governed records support watchers, comments, mentions, and reactions.
  • Requirement and risk ownership is selected from named planning members, rather than by entering internal person identifiers. EPS does not ask operators to enter raw JSON for these workflows.
  • Handoff preparation now selects named signatories and creates the actual accountable package command, preserving the selected baseline, cutoff, links, signatories, and operator reason.
  • Handoff creation is replay-safe and all-or-nothing: the package, manifest, audit record, and command receipt are committed together.
  • Readiness gates now record Go, Modify, Postpone, or Cancel decisions through named approval-participant choices and plain-language exceptions/rationale. The gate decision, state transition, audit entry, and replay receipt commit together, so operators never need to enter raw JSON or internal person identifiers.
  • Gate review no longer shows an unused reviewer-assignment text field; the named approval-participant picker appears at the decision that records those approvals.
  • Event Configuration proposals now start with a readable EMS record picker and named field changes, rather than internal record IDs or JSON patches. Proposed updates remain governed and are not attendee-visible until authorized application.
  • File access and retention controls now use named planning roles and departments, plus retention and legal-hold choices, rather than typed policy lists. Changes remain audited and enforce the existing controlled-download boundary.
  • File uploads now send their selected classification and retention period as a governed multipart command. Operators choose the file and readable controls; they are not asked to paste an EPS record ID or structured data.
  • The Files register now shows actual version lineage and retention/hold status, with selected-file details for version history, encryption, checksum, and scan state. Storage locations remain hidden behind the authenticated download boundary.
  • Reminder, gate-decision, and handoff registers now show human-readable planning-member labels instead of internal person identifiers.
  • Notification destinations now save through a validated controlled command using readable delivery addresses/channels, subscriptions, quiet hours, and a write-only secret boundary. Invalid email routes and unsupported policy values are rejected before save.
  • Project Settings now saves lifecycle, calendar/template choices, access roles, retention, and an operator reason through a versioned EPS command. Operators select readable records and roles instead of entering settings JSON or internal IDs.
  • Meeting recurrence now uses readable repeat choices and an end date rather than a raw calendar-rule string. EPS derives the standards-compatible calendar value internally while preserving selected participants and reminders.
  • Department ownership and reminder-policy choices now use readable scoped pickers. EPS continues to keep operational IDs and structured command data out of operator-facing forms.
  • Meeting workflows include classified shared/confidential/facilitator notes plus draft/published/locked agenda revisions and pre-read deadlines. Published minutes remain immutable.
  • Every route-specific primary, secondary, filter, comment/mention, RSVP, review, history, retention, handoff, and audit/export dialog is implemented in the shared desktop dialog/mobile sheet system. The New Department dialog opens blank and includes identity, charter, accountable lead, capacity model, and effective date.
  • Email, Discord bot/webhook, and Telegram bot destinations use encrypted write-only secrets with test, rotation, revocation, routing, and durable delivery-history controls.
  • Ordinary task, requirement, and meeting writes materialize bounded idempotent reminders; edits reschedule them, completion cancels them, personal subscriptions/channels/snooze/quiet hours are enforced, and terminal provider failures can follow configured escalation routes.
  • Daily and weekly preferences now create real aggregated digest buckets rather than individual messages. The calendar export dialog offers iCalendar and JSCalendar; recurring meetings retain stable UIDs, sequences, and cancellation state.
  • Requirement review now supports sequential and parallel approval stages, reviewer quorum, and submitter/reviewer segregation. Governed detail panels render threaded replies, reactions, and watcher controls.
  • Settings now includes a fully designed preview-first bulk-import dialog for work, requirements, meetings, and risks. It validates up to 500 records, binds apply to the exact preview digest, commits one batch atomically, and preserves idempotent receipts.
  • New schedule dependencies deterministically move affected successor dates through working-week, holiday, blackout, and working-day exception rules and audit the affected item set.
  • Every upload uses Sanity through the authenticated Worker. Confidential or restricted bytes are encrypted before upload, Postgres keeps only metadata and opaque asset IDs, and no Sanity API/CDN URL is returned to clients.
  • Uploaded bytes enter a durable scan queue. A scheduled authenticated Worker decrypts only server-side for the trusted HTTPS scanner, quarantines detections, retries failures, and withholds downloads until a clean result.
  • Linked EPS and Event Management workspaces share the same canonical event, tiers, inclusions, add-ons, tier relationships, and Event Shop records. Planning proposals remain private until authorized application.
  • The canonical linked view also projects Dealers Den packages, programme forms, volunteer departments/positions, and redacted payment-setup references without copying them into EPS.

Impact

Event directors and department teams can coordinate convention readiness in one pre-event system without duplicating EMS, Rego, Finance, or AMS records. EPS remains visibly labelled Preview while security and canonical-data boundaries remain mandatory.

Deployment Order

  1. Review and apply the pending EPS migrations in timestamp order. The current dry-run requires explicit --include-all because local EPS and Finance migrations precede the remote migration tip.
  2. Deploy partners-api; configure the existing Sanity and notification secrets plus PLANNING_ARTIFACT_ENCRYPTION_KEY, PLANNING_NOTIFICATION_ENCRYPTION_KEY, PLANNING_MALWARE_SCAN_URL, and PLANNING_MALWARE_SCAN_TOKEN; then deploy partners.furries.ph.
  3. Enable EPS for a non-production partner, verify one linked EMS event, and test encrypted upload/download plus Email, Discord, and Telegram destinations.
  4. Confirm that pending planning proposals remain absent from attendee-facing Rego until applied.

Validation

  • Dashboard Astro diagnostics and static build pass; Worker TypeScript passes.
  • EPS contracts certify the auth boundary, canonical EMS link and scoped forms, attendee isolation, notifications/digests, staged approvals, meetings/RSVPs/threaded comments, iCalendar/JSCalendar, immutable records, malware scan queue, and Sanity-only media policy.
  • Browser evidence covers all ten routes and their primary/secondary/filter/comment/RSVP/bulk-import modals, plus the complete New Department dialog at desktop and 390px. Resilience evidence processes 10,000 work items, a 500-row import identity, and three reminder replays without duplicate logical sends. The production migration dry-run made no remote changes and reported the required migration-history reconciliation step.
2026-08-1306:37

AMS Certified Reference Policy

Repositories: partners.furries.ph, docs.furries.ph

Status: Ready for deployment review

What’s Changed

  • AMS Finance now includes a readable and downloadable management-policy reference with all twelve economic decisions populated.
  • The package includes owned-asset, third-party loaned-asset, and maintenance work-order examples plus an open JSON Schema and SHA-256 certification receipt.
  • Safety controls identify the package as sample-only, omit an effective date, and prohibit production activation. Teams must clone, adapt, and independently approve a real policy with different proposer and approver identities.
  • Fixed AMS tables and operation modals after navigation inside the persistent dashboard shell. Overview, registers, checkouts, transit, audits, maintenance, Logistics Hub, Finance, and Settings now initialize consistently after either a direct load or nested-sidebar navigation.
  • AMS is now visibly labelled Preview in its Workspace entry, AMS sidebar, and every AMS page header while operators evaluate the module.
  • AMS documentation now uses the same staged structure as Event Management: Foundations, Basics, Surfaces, Best Practices, Lifecycles, and Reference. Each of the ten AMS Workspace routes now has operator-facing guidance, with separate role, data, route, standards, and readiness references.
  • AMS register suggestions now remain clear of adjacent fields, stack above surrounding form content, expose their autocomplete state, and dismiss consistently with Escape or focus changes. QR/barcode/NFC label generation also falls back safely to the canonical resolver when an identifier response is incomplete.
  • Asset creation now includes in-context New category and New model actions. Each opens a focused nested master-record dialog, records the signed-in operator through the existing AMS catalog API, and automatically selects the newly created record without losing the asset draft.
  • All ten AMS routes continue through the persistent dashboard SPA shell. The transient ?action=add deep-link state no longer follows sidebar navigation, and Cancel/close controls work after direct loads and SPA transitions.

Impact

Asset and finance operators have a practical starting point instead of an empty policy packet, while auditors retain a clear boundary between certified software behavior and professional accounting decisions.

Validation

  • pnpm workspace-assets:certify:policy, dashboard diagnostics/build, and documentation diagnostics/build pass.
  • The 20-check AMS browser certificate covers direct loads, all ten primary route dialogs, nested category/model master-record dialogs on direct and SPA navigation, scanner and identity-label dialogs, mobile overflow, autocomplete spacing, the Finance reference-policy dialog, Add Asset query cleanup, and a real Overview → Checkouts SPA transition followed by opening and cancelling the checkout modal.
2026-08-1306:37

Partner Finance Hub Foundation

Repositories: partners.furries.ph, partners-api, docs.furries.ph

Status: Ready for deployment review; migrations required

What’s Changed

  • A new partner-wide Finance hub consolidates posted accounting activity from every event while preserving each event reference and drill-down scope.
  • Finance now uses an AMS-style nested management workspace with dedicated Overview, Transactions, Outflows, Reconciliation, Events, Audit trail, Automation, Settings, Payables, Receivables, Expenses & advances, Budgets & forecasts, Close & assurance, and Integrations pages, plus focused creation and action dialogs with responsive layouts.
  • The hub distinguishes available cash, money in, money out, pending outflows, unreconciled differences, event coverage, cash accounts, and complete journal lines instead of presenting one ambiguous total.
  • Authorized operators can post partner-wide or event-specific income, expenses, and cash transfers through a balanced-entry form; server-side account, currency, event, and open-period checks prevent malformed postings.
  • Authorized reviewers can download a bounded UTF-8 journal export using the same optional event scope as the dashboard; every export records its actor, cutoff, scope, and row counts in the audit trail.
  • Partner-wide entries can be allocated across owned events with exact reconciliation and immutable version history; posted mistakes are corrected with balanced linked reversals rather than edited in place.
  • Reconciliation now follows a preview-first statement workflow with row validation, source digests, a different signed-in reviewer for commit, immutable committed rows, per-account coverage, and audited soft close, hard close, and reopen controls.
  • Outflow requests bind the signed-in requester and authoritative server time, require independent approval, use optimistic version checks, and produce immutable action receipts and audit events.
  • Finance decisions now acquire a short renewable checkout for the signed-in team member; competing users are locked out, the lease is rechecked inside the same transaction as the decision, and the activity trail shows acquisition, action, and release times.
  • Payables, receivables, procurement, expenses, cash advances, budgets, forecasts, close checklists, and audit findings use a common event-aware subledger with maker-checker transitions, immutable final states, and accountable checkout.
  • Cash boxes and drawers record signed-in opening custody, movements, count-based handover independently acknowledged by both parties, closing variance, and separate supervisor review.
  • Evidence metadata is content-addressed with SHA-256, retention and legal-hold state, immutable history, and purpose-bound access records.
  • Versioned ISO 20022 statement, UBL 2.3 document, XBRL GL, and SAF-T-style adapters preserve canonical IDs, event scope, currency, source drill-down, and original provenance; integration health and continuity reconciliation controls appear in the hub.
  • Partner defaults and event-specific inherit, override, or disabled routing can send inflow and outflow updates to verified Telegram topics and Discord channels or threads.
  • Finance administrators can define default payment accounts once for the partner. They are copied to every current and future event checkout; editing an inherited event account creates a local override so later partner changes do not erase event-specific setup.
  • All Finance dialogs now use a centered responsive presentation. The settings workflow explains inheritance, availability, limits, account identifiers, and the signed-in audit trail without requiring operators to repeat setup event by event.
  • Telegram and Discord disbursement buttons accept only one active linked dashboard identity with current finance authority; provider identity, names, group roles, and forwarded payloads do not grant permission.
  • Notification delivery uses a transactional outbox, bounded retries, quarantine state, one-time opaque actions, and scheduled processing so a provider failure cannot alter or duplicate a ledger transition.

Deployment Order

  1. Apply the Finance migrations from partners.furries.ph in timestamp order, including 20260813230000_partner_finance_default_payment_accounts.sql and 20260813231000_partner_finance_security_hardening.sql. Apply only the pending forward migrations reported by the dry run.
  2. Configure the Discord interaction public key and existing bot/webhook secrets, then deploy partners-api.
  3. Deploy partners.furries.ph and verify finance access for one non-production partner.
  4. Configure test partner and event destinations, confirm the non-financial verification messages, then exercise request, approval, disbursement, and inflow posting paths.

Validation

  • The disposable database certification passes the finance invariants across service-only finance tables, covering balanced posting and reversal, immutable journals/imports/allocations/evidence, tenant isolation, idempotency, maker-checker, accountable checkout, custody handover, close/reopen, control bootstrap, continuity reconciliation, outbox commit, version conflicts, and receipts.
  • The local audit also passes an independent exact-money oracle, seeded mutation detection, 40,000 property cases, deterministic 16-actor contention, a 1,000,000-line performance fixture, logical restore/reconciliation, route/API inventory, and static dialog accessibility checks.
  • Worker TypeScript, dashboard Astro diagnostics/build, standards interchange, and desktop/mobile visual evidence pass locally. The complete gate intentionally remains pending until hosted migration/canary, authenticated Telegram and Discord provider tests, native backup/restore, cross-browser state coverage, and independent review are supplied.
  • In-app-browser checks opened all 17 tested Finance modal entry points, saved a partner-default payment account through the real form, and navigated all 14 Finance routes while retaining the persistent dashboard SPA shell. Centering assertions cover all 12 Finance dialog types.
2026-08-1306:37

Asset Management System Foundation

Repositories: partners.furries.ph, partners-api, docs.furries.ph

Status: In development

What’s Changed

  • A new standalone Asset Management System (AMS) separates Owned Assets from Loaned Assets held in FPH care.
  • The first dashboard workspaces cover registers, checkouts, transit, audits, maintenance, finance, and settings through EMS-style nested navigation.
  • The certified foundation records server-derived actors, immutable movements, QR/Code 128/Web NFC carriers, partial returns, reservations/transfers, audit and maintenance lifecycle, bulk container transit/exceptions, RLS isolation, and maker-checker economic entries.
  • Deterministic economics now cover currency, component replacement, prospective estimate changes, full depreciation schedules, NRV, impairment, inventory costing, TCO sensitivity, disposal, hard close, and external journal receipt reconciliation.
  • Mature hub controls now include assigned work, quality holds, dock state transitions, automatic min/max replenishment tasks, and RTO/RPO continuity exercises.
  • Audit closeout now documents blind counts, independent recounts, immutable variance posting, audit packs, and recovery; finance teams also have a formal policy-approval record for the remaining accountable sign-off.
  • Every AMS route now follows the Overview visual language with contextual metrics, searchable registers, and consistent button-launched operation dialogs. Known assets, locations, parties, catalogue entries, and agreements autocomplete with identifying detail; a shared camera QR/barcode, Web NFC, and manual resolver replaces prompt-based scanning.
  • EPCIS ObjectEvent/AggregationEvent fixtures pass GS1’s official 2.0.1 JSON Schema, every mapped CBV term resolves in the normative ontology, and sensitive exports/configuration require recent MFA/passkey step-up.

Impact

Partner teams can review the organization-scoped property model without coupling it to events, reports, or Pawsports. Migration/deployment and production-scale/recovery acceptance remain separate release gates.

Validation

  • Database invariants pass across 62 RLS-enabled AMS relations and 12 ordered migrations, including transit recovery, hub orchestration, economics, CSV imports, private evidence, alerts, EPCIS mapping, and transactional webhook outbox. Disposable resilience certification also passes a 500-scan burst, 1,002-asset snapshot, no-oversell contention, concurrent idempotency, and zero-loss checkpoint restore.
  • The Worker certifies 87 authenticated route contracts and 67 server-side commands, the official GS1 schema/ontology gate, recent-AAL2 controls, and TypeScript.
  • Dashboard and documentation Astro checks pass with zero errors; the repeatable AMS browser certificate passes 14 checks across all ten route/modal surfaces, rich autocomplete, deep links, scanner state, console health, and 390 px overflow.

All docs