Updates
Platform Updates
Public-facing release notes for meaningful changes across Furries PH operational systems.
First created Last updated
Partners V2 Planning event change sets
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning Event Configuration now restores the legacy canonical EMS change workflow. Authorized operators can propose a named-field change against a readable EMS record, use an authorized direct command where permitted, then review, reject, approve, and apply a change set. EMS remains the source of truth, and V2 does not create a copied event record or expose raw record identifiers and JSON patches.
Local type checking, production build, and a synthetic browser fixture passed. The fixture verifies the proposal, direct, review, and apply Worker commands. No live EMS record was changed.
Partners V2 Planning readiness pack
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators can now create the legacy Furcon readiness requirement pack in V2 against an optional department and a chosen deadline anchor. The generated requirements remain normal editable planning records, while the existing Worker calculates deadlines, checks authority, and retains the operation receipt.
Local type checking and a synthetic browser command check passed. No real requirements, Worker write, or deployment was created.
Partners V2 Planning requirement responses
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators can now submit a written or evidence-backed requirement response and record the legacy dashboard’s governed review decisions directly from a V2 Planning Requirements row. Evidence keeps its selected access classification and optional role or department policy. The Worker remains the authority for permissions, version checks, review eligibility, and the immutable history.
Local type checking and synthetic browser command checks passed. No real response, Worker write, or deployment was created.
Partners V2 Planning controls
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators can now view, create, and version-protect edits to governed obligations, controls, permits, policies, and standards in the V2 Risks workspace with the legacy dashboard’s full source, ownership, applicability, lifecycle, evidence, and review-date fields. The existing Worker continues to enforce access, member eligibility, state policy, and the audit record.
Local type checking and a synthetic browser command check passed. No real control, Worker write, or deployment was created.
Partners V2 Planning exercises
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators can now create tabletop exercises with the legacy dashboard’s scenario, participants, observers, timed injects, and corrective-action tracking. The existing Worker remains the authority for access and exercise records.
Local type checking passed. No real exercise, Worker write, or deployment was created.
Planning Settings can now export the bounded Worker audit record as a local JSON or CSV file with its cutoff and row-count manifest.
Planning Requirements now includes active membership-requirement templates with department/role targeting, relative due dates, assigned reviewers, classification, instructions, acceptance criteria, reminder timing, and idempotent creation.
Each editable Planning Requirement can now use the legacy multi-stage approval workflow, with ordered sequential or parallel reviewer stages, quorum, expiry, and submitter-separation rules.
Submitted requirement responses can also be withdrawn with a recorded reason. The previous response remains in the planning history, and a corrected response can be submitted afterward.
Planning Notifications now loads and lets authorized operators save the legacy dashboard’s per-project notification preferences, including channels, subscriptions, timezone, digest cadence, quiet hours, and snooze time.
Partners V2 Planning gate decisions
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators can now record the legacy dashboard’s immutable gate decisions, including a decision, rationale, and unresolved exceptions. The existing Worker continues to validate gate policy and preserve the audit record.
Local type checking and synthetic browser command checks passed. No real gate decision, review, handoff package, Worker write, or deployment was created.
Partners V2 Planning Files
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning operators with edit access can now upload evidence from the V2 Files workspace using the same classification, retention, and optional access-narrowing controls as the legacy dashboard. The existing Worker continues to scan, encrypt, audit, and enforce the final file-access policy.
Local type checking and a browser fixture passed with synthetic planning data. No real file, Worker write, or deployment was created. The same Files workspace also now supports immutable replacement versions and reasoned retention, legal-hold, and access-policy updates for existing evidence.
Partners V2 Planning schedule calendar
Repository: partners.furries.ph-v2 — local implementation, not deployed.
The Planning Schedule now has Agenda, Day, Week, and Month calendar views, matching the legacy dashboard. Moving through calendar dates and selecting work keeps the operator in the schedule workspace; existing governed actions remain available from the selected work item.
The same schedule also now includes a Gantt timeline with local zoom and Worker-calculated critical markers.
Authorized planning operators can also move scoped work through the same controlled board columns as the legacy dashboard. Each status change is checked and recorded by the existing Worker workflow.
The schedule now also presents the project work-breakdown hierarchy, including authorized parent-package and sibling-order controls.
Selected work items now expose their immutable change history from the existing planning audit record.
Local type checking and a no-write browser fixture passed with synthetic data. No real planning record, Worker write, or deployment was created.
Partners V2 Planning baseline comparison
Repository: partners.furries.ph-v2 — local implementation, not deployed.
The Planning schedule now shows the same approved-baseline selector and variance summary as the legacy dashboard. Teams can compare the current schedule’s Worker-calculated start and due-date variance for every loaded work item.
Local type checking and a no-write browser fixture passed with synthetic data. No real planning record, Worker write, or deployment was created.
Partners V2 Planning dependencies
Repository: partners.furries.ph-v2 — local implementation, not deployed.
Planning schedules now let authorized operators connect two scoped work items with the same dependency types and lead/lag controls as the legacy dashboard. The existing Worker still checks project boundaries, duplicate links, and cycles.
Local type checking and a browser fixture passed with synthetic planning data. No real dependency, Worker write, or deployment was created.