Inspiration
A green build should tell reviewers which commit ran, whether PostgreSQL really worked, what an agent observed and where human responsibility remains. PixSettle brings that evidence into GitLab around an existing MIT-licensed reconciliation prototype.
What it does
This Path B entry demonstrates Supervised post-code automation with GitLab Duo Agent Platform. A person assigns the restricted F3 reviewer. The flow checks identities, the merge request, exact-commit pipeline and structured test evidence, then posts advisory review. A person decides before Ready or Merge. The flow does not merge or deploy; end-to-end Hands-off is not proven.
The public Cloud Run sandbox exposes actual Core health and read-only counts from ephemeral PostgreSQL. Homepage, /health and /sandbox/state returned 200. The observed database held one demo merchant and zero orders, events, outbox records and receipts; it resets at boot. Payment mutations, settlement, signed receipts, durable payment state, real money and external models are unavailable. This is not a completed payment workflow.
How we built it
We preserved the original Git history and added GitLab CI, a restricted review flow, measured PostgreSQL evidence and native AMD64 Cloud Build. MR4 and the README-only MR6 were merged by a person. The published source is e5117f02bfd579dedd3bcb1096236aa4ed5ccc99. Web pipeline 2970683683 passed on that exact SHA: core typecheck/PostgreSQL 16.15/314 passed + 1 skipped, and settlement typecheck/24 passed + 1 skipped. Anonymous job logs, original JUnit XMLs and job/SHA-bound PostgreSQL JSON evidence were verified. The separate runtime-proof testcase is CI instrumentation, not an extra application test. MR4's earlier agent review remains scoped to 4c466d9f/pipeline 2969381140.
Exact final Web pipeline · core/PostgreSQL job · settlement job.
Build v2 succeeded. Registry, public production and private staging agree on its image digest. The build archive predates configuration commit ff25477; recipe bytes match that later commit, without a claim that the build fetched that Git SHA.
Challenges and lessons
F3 session 9781186 finished with 25 actions and advisory approve in note 4053901181. It used job/SHA-bound PostgreSQL JSON evidence, while trace 404 and partial diff coverage remained explicit. It did not independently audit cloud or repository history. The lesson: retain evidence gaps instead of turning an agent's verdict into a broader guarantee.
A separate historical scan retained 24 findings / exit 42. Exact-source context review qualified all 24, including a negative-fixture identifier origin. A ten-head/three-tag snapshot matched that scan's manifest; later README-only deltas are reviewed separately. This is qualified source review, not a claim of complete security.
Current stage
The app and MIT-licensed GitLab repository are public; anonymous source, license, pipeline history, job logs and test artifacts were checked. MR4 and README-only MR6 are merged. The narrated English demo with captions, about 2m12, is published unlisted: https://youtu.be/4Nrv7JEQQ_s. The demonstrated automation level remains Supervised.
Built With
- gitlab
- postgresql
- typescript
Log in or sign up for Devpost to join the conversation.