Repository navigation
docs enterprise backlog ep20 release
Task IDs, titles, phase, cut, type, effort, priority and dependencies follow the existing generated index. Task descriptions were reconstructed from milestone validation, enterprise roadmap and F0 decisions.
Local F1 requires M0 closure and protected integration of the current ADR-019 construction batch. See the sequencing decision.
Gate tasks require actual executed evidence. Recovery of this backlog accepts no runtime milestone.
- Meta: module REL · phase F2 · cut C1 · priority P0 · type TEST · size M · state TODO
- Objective: Prove C1 from company setup to reviewed fueling with a synthetic receipt.
- Rules and use cases: BR-TEN-007, BR-OFFL-004, VAL-01, VAL-02, VAL-05, VAL-06, VAL-07, VAL-08, VAL-21
- Depends on: EMP-TRIP-006, EMP-TRIP-005, EMP-FUEL-012, EMP-FUEL-011, EMP-DOC-015, EMP-DOC-014, EMP-APPR-005, EMP-OFFL-014, EMP-OFFL-010, EMP-OFFL-007, EMP-OFFL-004, EMP-ORG-014, EMP-IDN-016, EMP-FLEET-012, EMP-METER-003, EMP-AUTH-009, EMP-AUTH-004, EMP-PUB-001, EMP-PRIV-003, EMP-PLAT-013
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: end-to-end scenario, PostGIS, Android and two-organization fixture · out: real-data pilot acceptance
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: Every declared C1 scenario passes on one revision and each unavailable manual item remains explicitly owed.
- Acceptance: Every declared C1 scenario passes on one revision and each unavailable manual item remains explicitly owed.
- Negative cases: Missing required scenario, mock-only proof, cross-organization exposure or synthetic success called production acceptance.
- Validation: V-E2E, V-SQL, V-APP, V-AUTHZ, V-ISO, V-SYNC, V-MONEY, V-PRIV · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
- Meta: module REL · phase F2 · cut C1 · priority P0 · type REL · size S · state TODO
- Objective: Rehearse scoped activation, rollback and recovery after C1 source acceptance.
- Rules and use cases: VAL-24, BR-AUTH-009, BR-PRIV-011, OQ-02
- Depends on: EMP-REL-001, EMP-PLAT-005, EMP-GOV-005, EMP-GOV-012
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: approved environment and named synthetic organizations · out: real pilot before legal and release gates
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: Flag changes preserve existing records and rollback and restore follow tested commands.
- Acceptance: Flag changes preserve existing records and rollback and restore follow tested commands.
- Negative cases: Unreviewed environment, erased data, missing read-time privacy gate or real activation from a local checkpoint.
- Validation: V-E2E, V-SQL, V-AUTHZ, V-ISO, V-PRIV · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
-
Status (2026-11-16): prerequisite LOCAL_DONE / INTEGRATION_PENDING on
codex/enterprise-activation: the ordinary runtime role, its generated grant inventory (infra/db/runtime-role.sql), the composed-process proof under that role and the VPS activation runbook with rollback (evidence, EDR-363..366). The task stays TODO: EMP-REL-001, the VAL-24 switch rehearsal and the activation itself remain owed.
- Meta: module REL · phase F1 · cut - · priority P1 · type TEST · size S · state TODO
- Objective: Accept M1 only after current-scope access and isolation evidence.
- Rules and use cases: VAL-02, VAL-03, VAL-21, VAL-22, BR-AUTH-006
- Depends on: EMP-AUTH-009, EMP-IDN-008, EMP-IDN-010, EMP-ORG-009
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: routes added in F1 and revocation/last-owner cases · out: capability claim from compile-only evidence
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: Current role and scope controls pass at normal entry points with the global flag off by default.
- Acceptance: Current role and scope controls pass at normal entry points with the global flag off by default.
- Negative cases: Missing denial case, overprivileged test role, ownerless organization or stale session access.
- Validation: V-E2E, V-SQL, V-AUTHZ, V-ISO, V-PRIV · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
- Meta: module REL · phase F3 · cut - · priority P1 · type TEST · size M · state TODO
- Objective: Accept M3 after exact cost, review, allocation and consumption evidence.
- Rules and use cases: EDR-013, BR-MONEY-007, VAL-08, VAL-09, VAL-10, VAL-11, VAL-12, VAL-13, VAL-14, VAL-19, VAL-20, VAL-25
- Depends on: EMP-DOC-010, EMP-FIN-004, EMP-BUDG-004, EMP-APPR-004, EMP-FUEL-008
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: full milestone scenarios on one revision · out: narrowing known failure coverage
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: No duplicate cost or budget race remains and corrected inputs update versioned results.
- Acceptance: No duplicate cost or budget race remains and corrected inputs update versioned results.
- Negative cases: Double counting, missing money vectors, unsupported ratio or a failed scenario waived.
- Validation: V-E2E, V-SQL, V-AUTHZ, V-ISO, V-IDEM, V-MONEY, V-SYNC · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
- Meta: module REL · phase F4 · cut - · priority P1 · type TEST · size M · state BLOCKED
- Objective: Accept M4 trips, sync resilience and authorized tracking fundamentals.
- Rules and use cases: BR-OFFL-011, BR-AMD-001, VAL-04, VAL-22, VAL-23, VAL-26, VAL-27, VAL-28
- Depends on: EMP-OFFL-013, EMP-TRIP-015, EMP-GPS-006, EMP-GPS-010
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: scenario union, source and device evidence · out: real tracking before its legal and device gates
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: Required interruption and late-intake cases pass or tracking remains held with owed evidence named.
- Acceptance: Required interruption and late-intake cases pass or tracking remains held with owed evidence named.
- Negative cases: Missing device coverage called pass, private fixtures committed, silent queue loss or location resumed without authority.
- Validation: V-E2E, V-SQL, V-APP, V-AUTHZ, V-ISO, V-SYNC, V-PRIV · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
M4 gate run on 1ee50c9e, 2026-11-16:
M4 NOT ACCEPTED; the task is BLOCKED (EDR-361). B-BR-EMP-552..555,
BUC-EMP-283/284 and EDR-360..362 precede the run; no behaviour, test or
migration. The source/host scenario union (real PostGIS, pure Go, Kotlin host
suites, mobile guard) passes; owed and blocking: the native stages on
emulator-5588 (locked behind its synthetic credential), the real-device
tracking interruption matrix on at least three manufacturers (EMP-GOV-006,
owner or pilot users), held fuelings for VAL-04/VAL-22 (EMP-FUEL-003), VAL-23
(f) clock skew, VAL-27 display and review (EMP-TRIP-006, UC-GPS-08), a single
cross-surface VAL-02 sweep, and the M3 gate (EMP-REL-004). Tracking collects
from no real employee until the matrix passes (EDR-362).
- Meta: module REL · phase F7 · cut - · priority P1 · type TEST · size M · state TODO
- Objective: Accept M7 only under recorded Stage D scope and review staffing.
- Rules and use cases: VAL-17, VAL-33, VAL-34, CX-05, BR-SRC-002
- Depends on: EMP-CLAIM-006, EMP-STN-010, EMP-AGREE-009
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: claim concurrency, neutrality and transactional sharing · out: public authority from payment
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: Approved scope and each scenario are evidenced on the named revision with staff readiness.
- Acceptance: Approved scope and each scenario are evidenced on the named revision with staff readiness.
- Negative cases: Missing override, competing live holders, private transaction leak or paid trust.
- Validation: V-E2E, V-SQL, V-WEB, V-AUTHZ, V-ISO, V-IDEM, V-PRIV · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
- Meta: module REL · phase F8 · cut - · priority P1 · type TEST · size M · state TODO
- Objective: Accept M8 only with approved billing and redistribution rights.
- Rules and use cases: VAL-18, VAL-35, VAL-36, EDR-024, EDR-025
- Depends on: EMP-SUBS-005, EMP-DATA-007, EMP-SUBS-004
- Read first: milestone validation, enterprise roadmap and F0 decisions
- Scope: in: event replay, capability state and Data privacy scenarios · out: enabling sale from a test result alone
- Areas: existing: scenario fixtures and affected normal entry points · proposed: milestone evidence and acceptance commands
- Steps: Pin the stated acceptance and denial cases before changing the owning entry point. Verify the affected consumers.
- Deliverable: Subscription effects and keys follow current authority and market datasets exclude private data.
- Acceptance: Subscription effects and keys follow current authority and market datasets exclude private data.
- Negative cases: Unverified provider event, role granted by payment, unlicensed source or hidden private row.
- Validation: V-E2E, V-SQL, V-AUTHZ, V-ISO, V-IDEM, V-MONEY, V-PRIV · migration: rehearse additive upgrade and recovery if persistent state changes · rollback: close the new entry and preserve accepted evidence
- Risks and assumptions: Each gate retains immediate critical checks, current-head evidence and distinct local, integration and production states.
- Done when: The stated result and denials pass the listed validation profiles.
- Home
- Roadmap
- docs-README
- docs-android-build
- docs-android-design-system
- docs-android-forum
- docs-android-games
- docs-android-map-engine
- docs-android-navigation
- docs-android-ocr-image
- docs-android-ocr-live-framing
- docs-android-premium-area
- docs-android-premium-integration
- docs-android-release
- docs-android-ui-containers
- docs-architecture-android-stack
- docs-architecture-android
- docs-architecture-backend
- docs-architecture-data-sources
- docs-architecture-overview
- docs-architecture-sources-ev-research
- docs-architecture-sources-national-limits
- docs-architecture-sources-national-stations
- docs-architecture-sources-register
- docs-assets-app-tutorial-CAPTURE_CONTRACT
- docs-assets-app-tutorial-FABLE_LANDING_POLISH_PROMPT
- docs-assets-app-tutorial-README
- docs-assets-attribution
- docs-assets-brand-README
- docs-assets-flags-ATTRIBUTION
- docs-assets-fuel-icons-README
- docs-assets-games-fuel-v1-README
- docs-assets-home-icons-README
- docs-assets-landing-fleet-android-20261012-BRIEF
- docs-assets-landing-hero-20261011-BRIEF
- docs-assets-landing-illustrated-20261012-BRIEF
- docs-assets-landing-illustrated-20261012-README
- docs-assets-landing-minimal-20261012-BRIEF
- docs-assets-landing-open-data-20261026-BRIEF
- docs-assets-landing-redesign-20261011-PREPARATION_EVIDENCE
- docs-assets-landing-redesign-20261011-README
- docs-assets-landing-redesign-20261011-REFERENCE_BRIEF
- docs-assets-landing-sync-20261012-BRIEF
- docs-assets-map-icons-README
- docs-backend-anp-ingestion
- docs-backend-api
- docs-backend-community-pricing
- docs-backend-data-model
- docs-backend-domain-model
- docs-backend-driver-private-data
- docs-backend-forum-architecture
- docs-backend-forum-bulletins
- docs-backend-forum-sources
- docs-backend-payments-provider-admission
- docs-backend-payments-provider-register
- docs-backend-photos-capture
- docs-backend-photos-subset-submission
- docs-backend-premium-api
- docs-backend-premium-cloud-protocol
- docs-backend-testing
- docs-backend-toolchain
- docs-brand-app-icons
- docs-brand-identity
- docs-decisions-001-kotlin-compose-stack
- docs-decisions-002-price-import-immutability
- docs-decisions-003-nominatim-reverse-geocode
- docs-decisions-005-modular-monolith-and-postgresql
- docs-decisions-006-official-catalog-and-exact-contracts
- docs-decisions-007-anonymous-proof-of-possession
- docs-decisions-008-privacy-and-retention
- docs-decisions-009-community-consensus-and-projections
- docs-decisions-010-private-object-evidence
- docs-decisions-012-licensing-and-hosted-business
- docs-decisions-015-kotlin-multiplatform-shared-domain
- docs-decisions-016-android-commercial-community-ios-deferred
- docs-decisions-017-station-profile-and-verified-representation
- docs-decisions-021-community-first-contribution
- docs-decisions-022-comaps-derived-native-map-engine
- docs-decisions-023-admin-suite-granted-tiers-contributors
- docs-decisions-025-private-abastevo-empresas-organization-boundary
- docs-decisions-026-multilingual-public-site
- docs-decisions-README
- docs-enterprise-README
- docs-enterprise-architecture
- docs-enterprise-backlog-INDEX
- docs-enterprise-backlog-ep00-governance
- docs-enterprise-backlog-ep01-platform
- docs-enterprise-backlog-ep02-organizations
- docs-enterprise-backlog-ep03-identity-access
- docs-enterprise-backlog-ep04-sync
- docs-enterprise-backlog-ep05-fleet-meters
- docs-enterprise-backlog-ep06-trips
- docs-enterprise-backlog-ep07-gps-navigation
- docs-enterprise-backlog-ep08-fuelings
- docs-enterprise-backlog-ep09-documents
- docs-enterprise-backlog-ep10-expenses-finance
- docs-enterprise-backlog-ep11-maintenance
- docs-enterprise-backlog-ep12-fuel-stock
- docs-enterprise-backlog-ep13-intelligence
- docs-enterprise-backlog-ep14-station-claims
- docs-enterprise-backlog-ep15-station-commerce
- docs-enterprise-backlog-ep16-subscriptions
- docs-enterprise-backlog-ep17-data
- docs-enterprise-backlog-ep18-imports-notifications-integrations
- docs-enterprise-backlog-ep19-back-office
- docs-enterprise-backlog-ep20-release
- docs-enterprise-business-rules
- docs-enterprise-contract
- docs-enterprise-conventions
- docs-enterprise-data-offering
- docs-enterprise-decisions
- docs-enterprise-domain-model
- docs-enterprise-glossary
- docs-enterprise-journeys
- docs-enterprise-modules-back-office
- docs-enterprise-modules-data
- docs-enterprise-modules-documents
- docs-enterprise-modules-expenses-finance
- docs-enterprise-modules-fleet
- docs-enterprise-modules-fuel-stock
- docs-enterprise-modules-fuelings
- docs-enterprise-modules-gps-navigation
- docs-enterprise-modules-identity
- docs-enterprise-modules-imports-notifications-integrations
- docs-enterprise-modules-intelligence
- docs-enterprise-modules-maintenance
- docs-enterprise-modules-organizations
- docs-enterprise-modules-station-claims
- docs-enterprise-modules-station-commerce
- docs-enterprise-modules-subscriptions
- docs-enterprise-modules-trips
- docs-enterprise-offline-sync
- docs-enterprise-permissions
- docs-enterprise-portal-routes
- docs-enterprise-privacy-security
- docs-enterprise-product-vision
- docs-enterprise-source-admission
- docs-enterprise-state-model
- docs-enterprise-testing
- docs-enterprise-ux-app
- docs-enterprise-ux-web
- docs-operations-README
- docs-operations-backup
- docs-operations-deploy-agent
- docs-operations-dou-editions
- docs-operations-edge-cache
- docs-operations-enterprise-activation
- docs-operations-map-static-overlay
- docs-operations-moderation-feedback
- docs-operations-moderation-profiles
- docs-operations-monitoring
- docs-operations-operator-access
- docs-operations-payments
- docs-operations-premium-billing
- docs-operations-recovery
- docs-operations-registry-daily-sync
- docs-operations-registry-runs
- docs-product-README
- docs-product-admin-tiers
- docs-product-community-community-first
- docs-product-community-experience
- docs-product-community-metrics
- docs-product-community-moderation
- docs-product-community-safety
- docs-product-community-terms-pt-br
- docs-product-driver-suite-README
- docs-product-driver-suite-android-state
- docs-product-driver-suite-cloud-sync
- docs-product-driver-suite-cost-profiles-and-maintenance
- docs-product-driver-suite-driver-model-and-earnings
- docs-product-driver-suite-foundation-decisions
- docs-product-driver-suite-gps-lifecycle
- docs-product-driver-suite-mobile-hub
- docs-product-driver-suite-odometer-review
- docs-product-driver-suite-outbox-wire
- docs-product-driver-suite-quick-refuel
- docs-product-driver-suite-reports
- docs-product-driver-suite-shifts-and-distance
- docs-product-driver-suite-signed-commands
- docs-product-ev-README
- docs-product-ev-charging-stop-planner
- docs-product-ev-energy-model
- docs-product-ev-financial-method
- docs-product-ev-journey-ui
- docs-product-ev-preparation
- docs-product-ev-typed-data
- docs-product-exploration
- docs-product-forum-contract
- docs-product-forum-policies
- docs-product-glossary
- docs-product-landing-content
- docs-product-landing-guides
- docs-product-landing-organic-growth-i18n-plan
- docs-product-licensing
- docs-product-map-discovery
- docs-product-map-favorites-and-trips
- docs-product-map-reports-routing-guidance
- docs-product-notification-content
- docs-product-official-prices
- docs-product-open-source-business
- docs-product-overview
- docs-product-payments-README
- docs-product-payments-offer-policy
- docs-product-premium-README
- docs-product-premium-financial-method
- docs-product-premium-source-policy
- docs-product-stations-catalog
- docs-product-stations-fuel-feedback
- docs-product-stations-fuel-quality
- docs-product-stations-identity-and-ev-catalog
- docs-product-stations-profile-contract
- docs-product-stations-profile-representation
- docs-product-stations-registry-sources
- docs-product-vehicle-registration
- docs-product-vehicles-and-occurrences
- docs-security-android-terms-acceptance
- docs-security-free-account-access
- docs-security-identity-profile
- docs-security-media-location-policy
- docs-security-privacy-notice
- docs-security-privacy-policy
- docs-security-retention
- docs-security-risks
- docs-security-security-privacy
- docs-store-README
- docs-store-play-readiness
- docs-store-play-store-listing
- docs-store-ugc-safety
Source: AlexandreZanata/Abastevo @ e4a67580fc368a59bc1c0f1e0466fc011313f330