Repository navigation
docs enterprise backlog ep08 fuelings
AlexandreZanata edited this page Nov 21, 2026
·
1 revision
Task IDs, titles, phase, cut, type, effort, priority and dependencies follow the existing generated index. Task descriptions were reconstructed from the fueling specification, validation scenarios and F0 decisions.
Local F1 requires M0 closure and protected integration of the current ADR-019 construction batch. See the sequencing decision.
The C1 fueling path uses the approved synthetic receipt scope. Consumption, reference comparisons, amendments and other later work keep their indexed dependencies.
- Meta: module FUEL · phase F3 · cut C1 · priority P0 · type API · size M · state TODO
- Objective: Review a fueling under current authority and preserve each decision.
- Rules and use cases: BR-FUEL-017, BR-FUEL-020, BR-FUEL-021, BR-REV-003, BR-REV-005, BR-REV-007, UC-FUEL-02, UC-FUEL-03, UC-FUEL-04
- Depends on: EMP-FUEL-002, EMP-APPR-001
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: check, approve, reject, return, cancel and scoped resubmission · out: approving one's own or a stale record
- Areas: existing: shared review component and scoped fueling store · proposed: fueling review routes and audit
- Steps: Pin each allowed transition, warning justifications and competing decisions. Keep prior revisions and expose authoritative results to the author.
- Deliverable: An audited fueling review API.
- Acceptance: One decision applies to the reviewed revision. Warning and duplicate resolution rules hold and cancellation follows the documented states.
- Negative cases: Author, payer or responsible employee approves, stale reviewer succeeds, missing required reason, or cancellation erases a reading.
- Validation: V-API, V-SQL, V-AUTHZ, V-ISO, V-IDEM, V-PRIV · migration: prove additive upgrade and recovery if persistent state changes · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type API · size M · state TODO
- Objective: Record a fueling establishment without modifying the public catalog.
- Rules and use cases: BR-FUEL-011, BR-FUEL-012, BR-FUEL-013, BR-FUEL-014, BR-SRC-004, UC-FUEL-05
- Depends on: EMP-FUEL-002, EMP-FLEET-009
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: read-only catalog link, private supplier or not-found entry · out: public station writes and device coordinates
- Areas: existing: directory read ports and organization suppliers · proposed: scoped fueling place links
- Steps: Verify authorized catalog reference, private supplier and typed fallback independently of issuer and contract roles.
- Deliverable: Scoped supplier linkage with a complete no-match path.
- Acceptance: A fueling can be complete without a public station. Linking changes only the fueling record.
- Negative cases: Foreign private supplier, typed name creates a station, raw location captured, or issuer overwritten by the place.
- Validation: V-API, V-SQL, V-AUTHZ, V-ISO, V-PRIV · migration: prove additive upgrade and recovery if persistent state changes · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type DOM · size S · state TODO
- Objective: Turn out-of-tolerance volume and incompatible products into review evidence.
- Rules and use cases: BR-FUEL-015, BR-FUEL-016, BR-FUEL-017, BR-FUEL-030
- Depends on: EMP-FUEL-002
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: exact capacity and compatibility warnings · out: silently rejecting or approving an observed event
- Areas: existing: fleet tank capacity and product rules · proposed: pure fueling warning decisions
- Steps: Pin the tolerance boundary, unavailable input and incompatible-product cases. Preserve the recorded event and require its documented review notes.
- Deliverable: Deterministic capacity and compatibility warning results.
- Acceptance: Warnings leave the field event intact and remain visible to the reviewer.
- Negative cases: Overflow, unknown capacity assumed zero, incompatible product treated as valid for consumption, or warnings silently dropped.
- Validation: V-DOM, V-MONEY · migration: none in this task · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type DOM · size S · state TODO
- Objective: Distinguish a technical resend from two recorded fuelings that look alike.
- Rules and use cases: BR-FUEL-018, BR-FUEL-019, BR-FUEL-020, BR-OFFL-004, UC-FUEL-07
- Depends on: EMP-FUEL-002
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: deterministic suspicion and review prerequisites · out: automatic merge, rejection or financial finding
- Areas: existing: scoped intake receipts and accepted fueling facts · proposed: duplicate signal rules
- Steps: Pin same-operation replay, time-window boundaries, independent records and review outcomes with synthetic vectors.
- Deliverable: A pure duplicate-suspicion decision and regression vectors.
- Acceptance: An identical resend creates no suspicion. Matching independent records stay visible and require a decision before approval when flagged.
- Negative cases: Resend creates another fact, different organization compared, one record silently merged, or suspicion treated as proof of duplicate payment.
- Validation: V-DOM, V-IDEM, V-MONEY · migration: none in this task · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type DOM · size L · state TODO
- Objective: Compute supported full-to-full intervals from approved fuel and meter evidence.
- Rules and use cases: BR-FUEL-025, BR-FUEL-026, BR-FUEL-027, BR-FUEL-028, BR-FUEL-029, BR-FUEL-030, BR-FUEL-031, BR-FUEL-032, EDR-011, VAL-10, VAL-11
- Depends on: EMP-FUEL-002, EMP-METER-006
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: anchors, ordered partial fills, exact sums and insufficiency · out: estimating consumption from one fill
- Areas: existing: exact-value and meter rules and personal full-to-full precedent · proposed: enterprise interval engine
- Steps: Pin opening and closing anchor arithmetic, readings, mixed products, gaps and partial-only histories with shared vectors.
- Deliverable: A pure full-to-full engine and reproducible interval results.
- Acceptance: An interval excludes the opening purchase and includes the closing one. Missing evidence produces the documented reason rather than a numeric result.
- Negative cases: Cross-segment readings, pending fact counted as approved, incompatible fuels, a partial fill used as an anchor or ratio averaging.
- Validation: V-DOM, V-MONEY · migration: none in this task · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type JOB · size M · state TODO
- Objective: Rebuild affected consumption intervals with revision and method provenance.
- Rules and use cases: BR-FUEL-032, BR-FUEL-033, BR-FUEL-034, BR-AMD-005, BR-TRUTH-004, UC-FUEL-09, VAL-20
- Depends on: EMP-FUEL-007
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: scoped projections, job replay and superseded results · out: changing source fueling or meter history
- Areas: existing: interval engine, owning events and jobs · proposed: interval projection and recomputation worker
- Steps: Pin corrections, voids and changed inputs. Rebuild the affected span and ensure duplicate or older jobs cannot overwrite a newer result.
- Deliverable: Versioned consumption projections with retry evidence.
- Acceptance: Changes affect only the relevant scope and produce an identifiable new revision when the result changes.
- Negative cases: Duplicate projections, stale event wins, missing basis, foreign asset or old number retained after insufficiency.
- Validation: V-SQL, V-JOB, V-IDEM, V-ISO, V-MONEY · migration: prove additive upgrade and recovery if persistent state changes · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut C1 · priority P0 · type WEB · size M · state TODO
- Objective: List and review scoped fuelings in the company panel.
- Rules and use cases: BR-FUEL-017, BR-FUEL-021, BR-AUTH-011, BR-PRIV-004, BR-REV-007, UC-FUEL-02, SCR-FUEL-06, SCR-FUEL-07
- Depends on: EMP-FUEL-003, EMP-PLAT-008
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: authorized list, detail, warnings and review actions · out: implicit document-content permission and client-side decisions
- Areas: existing: /empresas/ scaffold and fueling review API · proposed: accessible company fueling views
- Steps: Check scope, fresh results, concurrent decision conflicts and separate receipt permission through the company session.
- Deliverable: Scoped company fueling list, detail and review surfaces.
- Acceptance: Review state and warning reasons are visible. Denials or conflicts leave the original revision and records intact.
- Negative cases: Foreign result after switch, receipt bytes served through general read, stale review or self-approval.
- Validation: V-WEB, V-AUTHZ, V-ISO, V-PRIV · migration: none in this task · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type DOM · size S · state TODO
- Objective: Place retroactive fuelings in the true sequence without bypassing period locks.
- Rules and use cases: BR-FUEL-022, BR-FUEL-028, BR-FUEL-033, BR-AMD-004, BR-TIME-004, UC-FUEL-06
- Depends on: EMP-FUEL-007
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: effective ordering, late warning and affected interval basis · out: silently editing an approved or locked period
- Areas: existing: time and interval rules · proposed: retroactive-entry domain cases
- Steps: Pin neighboring readings, late thresholds, equal-time order and locked days. Test the recomputation handoff for affected intervals.
- Deliverable: A deterministic retrospective entry decision and affected-span result.
- Acceptance: The recorded instant is retained. Late and inconsistent evidence is surfaced under the current review and period rules.
- Negative cases: Device time overrides the lock, old interval silently stays current or a suspect reading fabricates a ratio.
- Validation: V-DOM, V-MONEY · migration: none in this task · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P2 · type API · size M · state TODO
- Objective: Preserve the source-specific price reference available at fueling acceptance.
- Rules and use cases: BR-FUEL-039, BR-SRC-001, BR-TRUTH-004, BR-KPI-012, UC-FUEL-11, VAL-15
- Depends on: EMP-FUEL-004
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: immutable snapshot of reference or unavailability per source · out: blending sources and treating a reference as a live paid price
- Areas: existing: official and community read models and fueling persistence · proposed: reference capture port
- Steps: Exercise no match, coverage and payment differences and repeated acceptance. Preserve origin, period, method and conditions.
- Deliverable: Scoped source-specific snapshot with deterministic replay.
- Acceptance: Each enabled source has an immutable value and basis or a reasoned unavailable state.
- Negative cases: Later source revision rewrites the snapshot, incompatible condition silently substituted, sources merged or no reference shown as zero.
- Validation: V-API, V-SQL, V-ISO, V-IDEM, V-MONEY · migration: prove additive upgrade and recovery if persistent state changes · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- Meta: module FUEL · phase F3 · cut - · priority P1 · type API · size S · state TODO
- Objective: Amend or void approved fuelings while preserving the original and period controls.
- Rules and use cases: BR-FUEL-023, BR-AMD-001, BR-AMD-002, BR-AMD-003, BR-AMD-004, BR-AMD-005, UC-FUEL-08
- Depends on: EMP-FUEL-003, EMP-PLAT-016, EMP-APPR-006
- Read first: fueling specification §§4–12, validation scenarios and F0 decisions
- Scope: in: scoped amendment, review and recalculation handoff · out: editing or deleting approved history in place
- Areas: existing: review API, period locks and amendment kernel · proposed: fueling amendment commands
- Steps: Pin prior revision visibility, period denial, competing decisions and downstream recalculation.
- Deliverable: Audited amendment and void commands with prior revision intact.
- Acceptance: The approved revision stays effective until a reviewed amendment applies. Locked-period work follows the authorized reopening or adjustment rules.
- Negative cases: Self-approval, stale revision, unreviewed lock bypass, lost original or duplicate effect in cost and consumption.
- Validation: V-API, V-SQL, V-AUTHZ, V-ISO, V-IDEM, V-MONEY · migration: prove additive upgrade and recovery if persistent state changes · rollback: close the new admission or projection path and preserve approved records, revisions and private data
- Risks and assumptions: The owning specification supplies business rules. Keep scope, synthetic C1 evidence and the applicable phase gates explicit.
- Done when: The stated outcomes and negative cases pass the applicable profiles at the affected entry points.
- 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