Repository navigation
docs enterprise backlog ep09 documents
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 approved receipt scope, domain model, state model, privacy and security and document requirements.
Local F1 requires M0 closure and protected integration of the current ADR-019 construction batch. See the sequencing decision.
The document specification now records the recovered design. This backlog uses the surviving shared rules and approved synthetic C1 scope. Real-receipt intake, retention and fiscal consultation retain their separate gates.
- Meta: module DOC · phase F3 · cut - · priority P1 · type API · size S · state TODO
- Objective: Record a human document review without changing fiscal or reconciliation claims.
- Rules and use cases: EDR-014, BR-TRUTH-001, BR-TRUTH-002, BR-REV-003, BR-REV-005, BR-REV-007, BR-AUD-001, REQ-10.2
- Depends on: EMP-DOC-003
- Read first: state model §3, domain model §3, document requirements §10
- Scope: in: authorized human review, outcome, reason and revision · out: fiscal consultation and automatic reconciliation
- Areas: existing: review and audit conventions · proposed: document review commands
- Steps: Pin review outcomes, required reasons and a stale-decision race. Store the reviewed revision separately from receipt and fiscal status.
- Deliverable: A scoped human-review workflow and immutable review evidence.
- Acceptance: The reviewer, time and outcome refer to one document revision. The reviewed status does not change a fiscal assertion.
- Negative cases: Self-review, stale revision, missing justification, cross-organization reviewer and a review overwriting the original document.
- Validation: V-API, V-SQL, V-AUTHZ, V-ISO, V-IDEM, V-PRIV · migration: rehearse additive review history · rollback: stop new decisions and preserve prior outcomes
- Risks and assumptions: Use the status names and review rules in the document design.
- Done when: Authorized and denied reviews pass with one auditable outcome per accepted decision.
- Meta: module DOC · phase F3 · cut - · priority P1 · type DB · size M · state TODO
- Objective: Link exact fiscal item amounts to expense allocations without recognizing a duplicate cost.
- Rules and use cases: BR-MONEY-001, BR-MONEY-004, BR-MONEY-007, BR-TEN-005, VAL-09, VAL-12, REQ-10.5
- Depends on: EMP-DOC-006, EMP-EXP-002
- Read first: domain model §§4–5, validation scenarios §4, document requirements §10
- Scope: in: fiscal item persistence and exact scoped allocations · out: creating a second expense from the same source
- Areas: existing: document and expense ports, exact-value conventions · proposed: item and allocation persistence
- Steps: Pin rounding vectors and concurrent allocation against the same source. Validate both item and document totals in the transaction.
- Deliverable: Fiscal items and allocations with tested amount and scope constraints.
- Acceptance: Allocated centavos reconcile with the recorded basis and cannot exceed the item or document total. A link alone does not recognize a cost.
- Negative cases: Race exceeds the source amount, incompatible units are added, foreign expense linked, or one receipt counted twice.
- Validation: V-SQL, V-ISO, V-IDEM, V-MONEY · migration: additive with populated upgrade · rollback: stop new allocations and keep reviewed history
- Risks and assumptions: Use the owning expense workflow for recognition and the canonical document rules for detailed fields.
- Done when: Exact arithmetic, race and rollback vectors pass on real PostGIS.
- Meta: module DOC · phase F3 · cut - · priority P1 · type DB · size S · state TODO
- Objective: Identify same-organization document duplicates without merging records automatically.
- Rules and use cases: BR-TEN-006, BR-TRUTH-002, BR-PRIV-008, BR-OFFL-004, REQ-10.4
- Depends on: EMP-DOC-002
- Read first: document requirements §10, domain model §5, privacy and security §4
- Scope: in: scoped key and digest matching for review · out: fiscal verification, cross-organization lookup and automatic merges
- Areas: existing: document metadata and digest verification · proposed: scoped duplicate checks
- Steps: Exercise matching key, matching bytes and changed-content retry cases with synthetic data. Keep duplicate evidence scoped.
- Deliverable: A scoped duplicate signal distinct from upload replay.
- Acceptance: A matching document can be presented for authorized review. An operation retry retains its original result.
- Negative cases: Cross-organization existence hint, hash treated as authenticity, a legitimate multi-link receipt automatically removed, or inconsistent concurrent matching.
- Validation: V-SQL, V-ISO, V-IDEM, V-PRIV · migration: rehearse additive lookup indexes · rollback: disable detection without changing documents
- Risks and assumptions: A repeated source and repeated transport are distinct. A signal does not determine review outcome.
- Done when: Matching, denial and concurrent intake tests pass on scoped fixtures.
- Meta: module DOC · phase F3 · cut - · priority P2 · type APP · size M · state TODO
- Objective: Offer optional on-device field extraction with explicit human confirmation.
- Rules and use cases: EDR-014, BR-TRUTH-001, BR-TRUTH-002, BR-PRIV-005, BR-PRIV-008, REQ-10.3
- Depends on: EMP-DOC-004
- Read first: document requirements §10, state model §3, privacy and security §4
- Scope: in: opt-in device extraction, field confidence and manual fallback · out: sending receipt content to an external extractor or approving values automatically
- Areas: existing: Android private attachment flow and device extraction precedent · proposed: enterprise extraction entry and field review
- Steps: Exercise unreadable and ambiguous fields. Preserve the original and distinguish suggestions from confirmed values.
- Deliverable: An optional on-device extraction flow with confidence and manual entry.
- Acceptance: Manual entry works independently. Extracted data has its own status and remains reviewable.
- Negative cases: Low-confidence value silently accepted, parser error blocks manual entry, raw content logged or extraction described as fiscal authorization.
- Validation: V-APP, V-PRIV, V-ISO · migration: preserve stored originals and user-confirmed fields · rollback: disable extraction and keep manual entry
- Risks and assumptions: The feature follows its own dependency and data-use review. It is outside synthetic C1 acceptance.
- Done when: Synthetic readable and unreadable cases pass without moving private bytes outside the approved partition.
- Meta: module DOC · phase F3 · cut - · priority P1 · type JOB · size M · state TODO
- Objective: Recompute document reconciliation from the current authorized operations and allocations.
- Rules and use cases: BR-TRUTH-001, BR-TRUTH-003, BR-TRUTH-004, BR-MONEY-007, BR-AMD-005, VAL-12, REQ-10.5
- Depends on: EMP-DOC-007
- Read first: domain model §§4–5, state model §3, validation scenarios §4
- Scope: in: idempotent reconciliation status and basis · out: fiscal status and changing the underlying paid amounts
- Areas: existing: scoped jobs and document/expense linkage · proposed: reconciliation worker
- Steps: Pin matched, divergent and insufficient-input outcomes. Recompute from versioned source state and converge on retry.
- Deliverable: A reconciliation result and reason tied to source revisions.
- Acceptance: The result describes reconciliation only. Reprocessing after changed inputs creates an identifiable result without duplicate cost.
- Negative cases: Incomplete data becomes matched, foreign operation enters a job, stale job supersedes a newer result or retry adds a second amount.
- Validation: V-SQL, V-ISO, V-IDEM, V-JOB, V-MONEY · migration: rehearse additive result storage if needed · rollback: pause jobs and preserve recorded results
- Risks and assumptions: The document design and state catalog govern reconciliation.
- Done when: Recompute, job failure, out-of-order delivery and scoped arithmetic cases pass.
- Meta: module DOC · phase F3 · cut - · priority P1 · type API · size S · state TODO
- Objective: Replace or cancel a document with an auditable history.
- Rules and use cases: BR-TRUTH-001, BR-TRUTH-002, BR-AMD-001, BR-AMD-003, BR-AUD-001, REQ-10.4
- Depends on: EMP-DOC-005
- Read first: state model §3, domain model §5, document requirements §10
- Scope: in: authorized replacement and internal cancellation references · out: deleting original evidence in place or claiming fiscal cancellation
- Areas: existing: document review, revision and audit conventions · proposed: replacement and cancellation commands
- Steps: Pin allowed transitions, stale revisions and concurrent replacement. Re-evaluate affected links or projections through owning workflows.
- Deliverable: A revision-aware document history and audited cancellation result.
- Acceptance: Old and new references are traceable. An internal outcome does not change an externally verified status.
- Negative cases: Foreign replacement, missing reason, duplicate revision under replay, original silently lost or internal cancellation shown as fiscal cancellation.
- Validation: V-API, V-SQL, V-AUTHZ, V-ISO, V-IDEM, V-PRIV · migration: preserve historical references · rollback: close new commands and keep prior changes
- Risks and assumptions: Original bytes follow the approved retention schedule rather than the convenience of a UI action.
- Done when: Revision, race and denial tests pass with audit and history intact.
- Meta: module DOC · phase F3 · cut - · priority P1 · type WEB · size M · state TODO
- Objective: Give company reviewers a scoped inbox, viewer and allocation workflow.
- Rules and use cases: BR-AUTH-011, BR-PRIV-004, BR-AUD-003, BR-MONEY-007, BR-TRUTH-001, REQ-10.5
- Depends on: EMP-DOC-005, EMP-DOC-007, EMP-PLAT-008
- Read first: document requirements §§10 and 20, privacy and security §4, approved receipt scope
- Scope: in: approved company panel document metadata, authorized content and review or allocation views · out: public or admin visibility
- Areas: existing: /empresas/ scaffold and owning document APIs · proposed: private document panel screens
- Steps: Exercise metadata-only access, content denial, revision conflicts and amount feedback through the existing company session.
- Deliverable: An accessible private document inbox and reviewer workflow.
- Acceptance: Each viewer action respects current permission and shows distinct review and reconciliation status.
- Negative cases: Foreign response after switching organizations, persistent object URL, misleading fiscal state and invalid allocation shown as saved.
- Validation: V-WEB, V-AUTHZ, V-ISO, V-MONEY, V-PRIV · migration: none · rollback: hide new views without dropping accepted records
- Risks and assumptions: Detailed screens follow the restored web and document specifications.
- Done when: Company panel role, scope, accessibility and conflict cases pass.
- Meta: module DOC · phase F3 · cut C1 · priority P0 · type WEB · size S · state TODO
- Objective: Show the authorized synthetic receipt within company fueling review.
- Rules and use cases: BR-AUTH-011, BR-PRIV-004, BR-AUD-003, BR-OFFL-015, BR-TRUTH-001, OQ-04, UC-PRIV-05
- Depends on: EMP-DOC-003, EMP-FUEL-012
- Read first: approved receipt scope, privacy and security §4, fueling specification
- Scope: in: same-organization C1 receipt viewer and pending or denied states · out: unreviewed real receipts and granting permission from fueling read access
- Areas: existing: company panel, fueling review and document link port · proposed: scoped embedded receipt viewer
- Steps: Exercise linked and pending synthetic receipts, separate content permission, expiry and audited access through the company session.
- Deliverable: A focused receipt view inside fueling review.
- Acceptance: An authorized reviewer opens only the linked document through an audited private capability. Review remains possible when the file is unavailable under its owning rules.
- Negative cases: Fueling read implies document bytes, expired or foreign capability works, or the UI treats a pending attachment as verified.
- Validation: V-WEB, V-AUTHZ, V-ISO, V-PRIV · migration: none · rollback: hide the viewer and preserve review records
- Risks and assumptions: Synthetic scope is approved for C1. Real-data activation has separate gates.
- Done when: The integrated viewer proves allowed, expired, pending and denied cases.
- 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