Open
Conversation
Update the live agent workflow to use the MVP implementation backlog and clarify how agents should handle MVP-scoped work. - add MVP planning references to AGENTS.md - expand docs/agent-workflow.md with task classification, scope control, docs-only validation, open-question corroboration, and multi-agent coordination guidance - add plans/mvp-gap-analysis.md as the current-state assessment companion to the MVP scope and backlog
Document the resolved chain/network discovery contract for MVP and add a sequencing guide derived from the MVP backlog. - mark MVP-033 as done and record the chosen package-derived network behavior in plans/mvp-implementation-backlog.md - narrow the corresponding open question in docs/mvp-scope.md - add docs/mvp-implementation-sequencing.md to describe dependency-driven implementation order and parallel work lanes
- prepare escrow, provision, provider registration, and demo signer authorization during shared devenv startup - simplify sds demo setup into demo-state verification plus env export only - update integration helpers/tests for the new default bootstrap behavior - switch .reflex to the deterministic demo signer and remove the obsolete .reflex.stack workflow
Rewrite the MVP scope, gap analysis, and implementation backlog so they reflect the agreed architecture and the current repo state. - make the consumer sidecar the primary SDS-facing boundary - align discovery, pricing, and session semantics with the revised MVP decisions - update gap and backlog status to reflect recent provider runtime and persistence work - narrow remaining open questions to auth and observability
juanmardefago
force-pushed
the
juanmardefago/mvp-scope
branch
from
a58efe7 to
799f001
Compare
juanmardefago
changed the title
- align the consumer/provider runtime contract around control-plane init, provider-returned data-plane endpoints, and fresh-session semantics - update sink/demo flows, generated protobufs, and integration coverage to match the revised MVP-004 behavior - make psql tests repo-portable, make integration devenv avoid fixed-port collisions, and refresh MVP backlog/gap-analysis status
- add a canonical provider persistence boundary doc for runtime vs settlement ownership - mark MVP-003 done and align backlog, sequencing, and gap-analysis wording - clarify in provider gateway docs that collection lifecycle tracking remains downstream work
- add session-local low-funds assessment, metadata persistence, and terminal NeedMoreFunds handling in PaymentSession - fix PaymentsEscrow balance queries to use the shared ABI-based getBalance encoding - add integration coverage for insufficient funds, exact-balance continue, unknown-balance fail-open, and consumer stop behavior - update MVP scope, backlog, sequencing, and gap-analysis docs to mark MVP-010 complete and freeze stop-only low-funds semantics
- add provider-side cost-based RAV request threshold policy with a 10 GRT fallback - load rav_request_threshold from provider pricing YAML without changing wire pricing contracts - add gateway and consumer integration coverage for below-threshold continue and post-baseline reset behavior - update MVP backlog, sequencing, gap-analysis, and scope docs to mark MVP-012 complete
- add a shared operator auth helper with bearer-token role checks and unit tests - document the MVP provider operator auth contract and narrow oracle whitelist management to internal governance - update MVP scope, backlog, sequencing, and gap analysis to mark MVP-028 resolved and align follow-on tasks
juanmardefago
changed the title
- strengthen the real provider-path firecore test harness with shared-repo evidence checks and blocker-aware runtime validation - harden provider auth/plugin handling for legacy malformed auth payloads while keeping current SDS contracts authoritative - document MVP-014 as blocked by protocol drift between current SDS and the prebuilt firecore/dummy-blockchain images
- add a local-first TestFirecore workflow that runs against rebuilt firehose-core and dummy-blockchain images via SDS_TEST_DUMMY_BLOCKCHAIN_IMAGE - align provider usage aggregation with current firehose-core metering names and stabilize firecore evidence checks in integration - update README, sequencing, and backlog docs to mark MVP-014 complete under the validated local runtime path and track upstream image publication in MVP-036
- make provider-side plugin metering update authoritative session usage and accumulated cost through a shared repository apply-usage path - thread provider pricing into the plugin usage service and cover the new session-aggregation behavior in repository and usage tests - tighten Firecore acceptance to verify live plugin activity advances gateway-visible payment status while preserving the existing PaymentSession flow
- reuse the provider pricing config in TestFirecore so the acceptance path checks the exact gateway-visible accumulated usage value - derive the expected total from persisted plugin metering evidence instead of only asserting that payment state became non-zero - keep the local-runtime Firecore integration as the proof that provider-side metering and gateway payment state remain exactly aligned
- update the backlog to close MVP-015 with the validated local-runtime acceptance evidence and exact Firecore verification path - move MVP-014 and MVP-015 into completed foundation work in the sequencing notes and promote MVP-016 as the next runtime-control task - record that the local-first Firecore workflow now proves plugin metering and gateway-visible payment state stay exactly aligned
- make provider session keepalive and worker acquisition fail closed for unknown or ended sessions, with payment exhaustion surfacing as resource exhausted and other invalid states as permission denied - align the SDS session plugin error mapping and extend Firecore integration coverage with a dedicated low-funds runtime stop path alongside the existing happy path - close MVP-016 in the backlog and sequencing docs while tracking the shared-state Firecore test hardening follow-up separately under MVP-037
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.