Data

Tools

Indexes

Applications

Experiments

Awesome

An open API service indexing awesome lists of open source software.

https://github.com/kolundzic/andyai-finance-engine

AndyAI Financial Modeling Engine — governed AI-assisted finance workflows
https://github.com/kolundzic/andyai-finance-engine

andyai finance-engine financial-modeling human-approval tapforge

Last synced: about 2 months ago
JSON representation

AndyAI Financial Modeling Engine — governed AI-assisted finance workflows

Awesome Lists containing this project

README 

          
# andyai-finance-engine



**AndyAI Financial Modeling Engine** is a governed AI-assisted financial modeling system for turning business documents, SaaS ideas, pricing plans, client proposals, and investor assumptions into structured financial models with verification, audit trails, and human approval gates.



> AI can build the model fast.  

> But the human must verify that the model tells the truth.



## Canon



- **Owner / Founder:** Andrija Kolundzic (Andy), Founder & Owner — Japan IT Business

- **Repo:** `andyai-finance-engine`

- **Version:** `v0.1.0`

- **Method:** TAP-TAP / Master Udarci

- **Core workflow:** Input → Extraction → Model → Verification → Human Approval → Export



## First bootstrap contents



- Canon metadata

- Architecture overview

- Workflow map

- Governance principle

- Input schema

- Example business input

- Verification script

- GitHub bootstrap script



## Public Showcase



AndyAI Finance Engine now includes a Next.js public showcase layer for Vercel deployment.



- `/` — public landing page

- `/workflow` — governed finance workflow

- `/demo` — working core demo preview

- `/library` — Finance Solutions Library preview

- `/proof` — proof and release line



### Public product canon



v1.0.0 = stable canon  

v2.0.0 = working core  

v3.0.0 = public showcase stable



## Supabase SaaS Foundation



v4.0.0 adds the Supabase SaaS foundation:



- `/supabase` — Supabase configuration status

- `/projects` — project workspace foundation

- `/runs` — model run evidence foundation

- `/audit` — audit trail foundation

- `/approval` — human approval gate foundation

- `supabase/migrations/` — database schema

- `supabase/policies/` — RLS policy draft



### SaaS canon



v1.0.0 = stable canon  

v2.0.0 = working core  

v3.0.0 = public showcase  

v4.0.0 = Supabase SaaS foundation



---



## v5.1.0 — Public Product Positioning Layer



AndyAI Finance Engine is a governed financial modeling workspace for founders, consultants, agencies, and business teams.



It helps transform business inputs, assumptions, pricing ideas, SaaS scenarios, investor logic, and operational plans into structured financial model drafts.



### Core Promise



Build financial models faster, but keep responsibility visible.



Financial modeling can be automated.  

Financial responsibility cannot be outsourced.



### Trust-First Position



AndyAI Finance Engine is not only about generating numbers.



It is designed around:



- assumption visibility

- human approval

- audit trail

- review status

- export safety

- monetization boundaries

- provider-neutral billing design



### Monetization Status



v5.1.0 is not a live billing release.



No checkout route, webhook, payment provider SDK, subscription enforcement, payment secret, or paid export runtime is active.



### Next Direction



The next major line is Supabase monetization setup: database-backed membership, quota, audit, and approval foundations.



---



## v5.2.0 — Supabase Monetization Setup Readiness



This checkpoint prepares AndyAI Finance Engine for Supabase-backed monetization setup.



Supabase will become the backend foundation for membership state, usage quotas, audit trail, approval state, export history, manual review, and future billing event mapping.



No live database runtime, migration, checkout, webhook, payment provider, or subscription enforcement is introduced in v5.2.0.



### Next Runtime Direction



- v5.3.0 — Membership Tables Draft

- v5.4.0 — Usage Quota Tables Draft

- v5.5.0 — Audit / Approval Tables Draft

- v5.6.0 — RLS Policy Draft

- v5.7.0 — Supabase Env + Setup Guide

- v5.8.0 — Local Verification Script

- v5.9.0 — Runtime Wiring Readiness

- v6.0.0 — Supabase Monetization Runtime Foundation



Supabase is not just a database.



In AndyAI Finance Engine, Supabase becomes the memory and governance substrate for monetized financial modeling.



---



## v5.3.0 — Membership Tables Draft



Adds draft Supabase membership tables for workspaces, workspace members, and membership states. Draft only; no live migration is applied.



---



## v5.4.0 — Usage Quota Tables Draft



Adds draft Supabase quota tables for quota policies, usage events, and quota windows. Draft only; no runtime enforcement is active.



---



## v5.5.0 — Audit and Approval Tables Draft



Adds draft Supabase tables for audit events, approval decisions, export records, and manual review queue.



---



## v5.6.0 — RLS Policy Draft



Adds a first conservative Row-Level Security draft for Supabase monetization tables. Draft only; review required before live use.



---



## v5.7.0 — Supabase Env and Setup Guide



Adds Supabase environment setup guidance and . No live Supabase runtime behavior is introduced.



---



## v5.8.0 — Local Verification Script



Adds 🟢 AndyAI Finance Engine — Supabase Monetization Foundation Verification

🟢 Found: docs/supabase/SUPABASE_MONETIZATION_SETUP_READINESS_v5.2.0.md

🟢 Found: docs/supabase/MEMBERSHIP_TABLES_DRAFT_v5.3.0.md

🟢 Found: docs/supabase/USAGE_QUOTA_TABLES_DRAFT_v5.4.0.md

🟢 Found: docs/supabase/AUDIT_APPROVAL_TABLES_DRAFT_v5.5.0.md

🟢 Found: docs/supabase/RLS_POLICY_DRAFT_v5.6.0.md

🟢 Found: docs/supabase/SUPABASE_ENV_SETUP_GUIDE_v5.7.0.md

🟢 Found: docs/supabase/sql-drafts/v5.3.0_membership_tables_draft.sql

🟢 Found: docs/supabase/sql-drafts/v5.4.0_usage_quota_tables_draft.sql

🟢 Found: docs/supabase/sql-drafts/v5.5.0_audit_approval_tables_draft.sql

🟢 Found: docs/supabase/sql-drafts/v5.6.0_rls_policy_draft.sql

🟢 Found: .env.example

🟢 No tracked .env.local detected

🟢 Verification complete to verify required Supabase monetization foundation files locally.



---



## v5.9.0 — Runtime Wiring Readiness



Defines future runtime wiring requirements for server-side Supabase access, membership lookup, quota reads, audit inserts, approvals, exports, and manual review.



---



## v6.0.0 — Supabase Monetization Runtime Foundation



Completes the Supabase monetization foundation at documentation and schema-draft level. No live database runtime or payment behavior is activated.



---



## v6.1.0 — Runtime Contract Types



Adds provider-neutral TypeScript contract types for future Supabase runtime work. No live database or billing behavior is active.



---



## v6.2.0 — Membership Repository Interface



Adds a future-facing membership repository interface for workspace access state. Interface only; no live Supabase calls.



---



## v6.3.0 — Quota Runtime Interface



Adds future-facing quota runtime interfaces. No live enforcement or Supabase calls are active.



---



## v6.4.0 — Audit Approval Runtime Interface



Adds future-facing audit and approval runtime interfaces. Interface only; no live database writes.



---



## v6.5.0 — Export Safety Gate



Adds a pure local export safety gate for future export workflows. No paid export runtime is active.



---



## v6.6.0 — Manual Review Runtime Interface



Adds future-facing manual review runtime interfaces. Interface only; no live queue writes.



---



## v6.7.0 — Runtime Boundary Index



Adds a single TypeScript export index for Supabase runtime foundation contracts. No live runtime behavior is active.



---



## v6.8.0 — Runtime Verification Script



Adds a local verification script for Supabase runtime foundation files.



---



## v6.9.0 — v7 Runtime Readiness Checklist



Adds readiness checklist for v7.0.0 Governed Runtime Foundation.



---



## v7.0.0 — Governed Supabase Runtime Foundation



Completes the governed Supabase runtime foundation at contract and verification level. No live database or payment behavior is activated.



---



## v7.1.0 — Supabase Live Setup Boundary



Defines the boundary between repository preparation and real Supabase setup. Real setup should start after v8.0.0.



---



## v7.2.0 — Migration Bundle Map



Adds a migration bundle map and placeholder folder for future reviewed Supabase migrations. No migration is applied.



---



## v7.3.0 — Env Local Guard



Adds a local guard script for Supabase environment variables. It passes before setup and can run strict after env values are added.



---



## v7.4.0 — Supabase CLI Preflight



Adds a non-blocking Supabase CLI preflight script. No live Supabase command is executed.



---



## v7.5.0 — Migration Application Runbook



Adds a runbook for future Supabase migration application. No migration is applied.



---



## v7.6.0 — RLS Review Gate



Adds RLS review gate and role matrix questions. No live RLS policy is applied.



---



## v7.7.0 — Vercel Env Sync Checklist



Adds Vercel environment sync checklist for future Supabase activation. No Vercel env change is performed.



---



## v7.8.0 — Live Setup Verification Pack



Adds combined live setup preflight verification script. It does not connect to Supabase or apply migrations.



---



## v7.9.0 — v8 Activation Readiness



Adds readiness checklist for v8.0.0 Supabase Live Activation Gate. No live setup is performed.



---



## v8.0.0 — Supabase Live Activation Gate



Completes the Supabase live activation gate. This is the point after which human-controlled real Supabase setup may begin.



---



## v8.1.0 — Supabase Free Account Deployment Strategy



This checkpoint defines how AndyAI Finance Engine should use a Supabase Free account safely.



### Decision



Do not duplicate all finance tables inside TAPFORGE as a second source of truth.



Use this model:



- AndyAI Finance Engine owns finance schema, SQL drafts, runtime contracts, and activation safety rules.

- TAPFORGE orchestrates installation, verification, operator approval, and evidence logs.

- Supabase Free is a lab/proof environment, not production.

- Production waits for a deliberate upgrade path.



### Rule



Free Supabase is a proving ground.



TAPFORGE is the orchestrator.



Finance Engine is the source of truth.



---



## v8.2.0 — TAPFORGE Migration Pack Manifest



Adds the TAPFORGE migration pack manifest. Finance Engine remains source-of-truth; TAPFORGE is orchestrator and evidence logger.



---



## v8.3.0 — Finance Engine Migration Import Contract



Defines how TAPFORGE may import Finance Engine migration material without becoming a duplicate source of truth.



---



## v8.4.0 — TAPFORGE Apply Dry Run Contract



Adds the dry-run contract required before TAPFORGE applies any Finance Engine migration pack.



---



## v8.5.0 — Namespace Registry



Adds namespace and prefix strategy for shared Supabase Free lab usage.



---



## v8.6.0 — Migration Evidence Ledger Contract



Adds evidence ledger contract for TAPFORGE-controlled Finance Engine migration operations.



---



## v8.7.0 — TAPFORGE Pack Verification Script



Adds verification script for TAPFORGE migration pack files and JSON manifests.



---



## v8.8.0 — Supabase Free Lab Seed Policy



Adds seed-data policy for a Supabase Free lab. No seed data is inserted.



---



## v8.9.0 — v9 TAPFORGE Handoff Readiness



Adds readiness checklist for v9.0.0 TAPFORGE Migration Orchestration Gate.



---



## v9.0.0 — TAPFORGE Migration Orchestration Gate



Completes the TAPFORGE migration orchestration gate. Finance Engine defines; TAPFORGE orchestrates and records evidence. No migration is applied.



---



## v9.1.0 — Supabase Lab Project Setup Runbook



This checkpoint adds the first safe Supabase Lab setup runbook.



### Meaning



The repo is ready for a human operator to create a Supabase Free lab project and configure local `.env.local` safely.



### Boundary



v9.1.0 does not create a Supabase project automatically.



It does not add secrets.



It does not apply migrations.



It does not activate production database runtime.



### Rule



Create the lab.



Protect the secrets.



Verify the gate.



Do not migrate until the system can explain what it is doing.



---



## v9.2.0 — Local .env Setup Assistant



This checkpoint adds a local Terminal assistant for creating `.env.local` safely.



### Command



```bash

./scripts/create-supabase-env-local.sh

```



### Rule



Secrets stay local.



The system can verify their presence without exposing their values.



Do not paste service role keys into chat, README, GitHub, screenshots, logs, or public notes.



---



## v9.3.0 — Supabase Lab Connection Smoke Test



This checkpoint adds a local Supabase Lab connection smoke test.



### Command



After `.env.local` is created locally:



```bash

./scripts/smoke-test-supabase-lab-connection.sh

```



### Rule



The smoke test proves connection only.



It does not apply migrations.



It does not create tables.



It does not prove production readiness.



---



## v9.3.1 — Publishable Key Smoke Test Fix



This patch updates the Supabase Lab smoke test to use the Auth health endpoint:



```text

/auth/v1/health

```



The previous REST-root smoke test could return `Secret API key required` when using `sb_publishable_` keys.



The smoke test now proves project reachability without requiring elevated database access.



---



## v9.4.0 — Supabase Lab Migration Review Pack



This checkpoint adds the review pack required before any Supabase Lab migration is considered.



### Rule



No migration apply before:



- SQL draft inventory review

- RLS review

- namespace decision

- env guard

- smoke test

- TAPFORGE dry-run evidence

- human operator approval



Migration review is the firewall between a useful lab and a damaged database.



---



## v9.5.0 — Supabase Lab Dry-Run Migration Plan



This checkpoint adds the dry-run migration plan before any Supabase Lab SQL apply is considered.



### Rule



Dry-run is not apply.



Dry-run creates a reviewable SQL preview bundle and evidence template.



No database mutation is performed.



---



## v9.6.0 — Supabase Lab SQL Apply Candidate Gate



This checkpoint adds the candidate gate before any future lab-only SQL apply script may be prepared.



### Rule



A candidate gate is not permission.



It is a controlled pause before permission can even be discussed.



No SQL apply happens in v9.6.0.



---



## v9.7.0 — Supabase Lab Namespace Decision Lock



This checkpoint locks the namespace decision for the shared Supabase Free lab.



### Decision



Use prefix-based isolation first:



- `fe_` for Finance Engine

- `tf_` for TAPFORGE

- `audit_` for shared audit

- existing Human Attention tables remain protected and untouched



### Rule



No prefix lock, no apply.



No SQL apply happens in v9.7.0.



---



## v9.8.0 — Prefixed SQL Preview Bundle



This checkpoint adds the prefixed SQL preview bundle after the namespace decision lock.



### Rule



Preview is not apply.



The preview uses `fe_` table names and ends with `ROLLBACK`.



No SQL apply happens in v9.8.0.



---



## v9.9.0 — Lab-Only Apply Script Candidate



This checkpoint prepares a guarded lab-only SQL apply candidate.



### Rule



The TAP release does not apply SQL.



The candidate script is disabled by default and requires:



- explicit environment gate

- exact confirmation phrase

- strict env guard

- smoke test

- prefixed preview verifier

- candidate verifier

- reviewed lab-only DB URL



A loaded tool is not a fired tool.



---



## v9.9.1 — Lab Apply Tooling Preflight



This checkpoint adds tooling preflight checks before any future lab-only SQL apply attempt.



### Command



```bash

./scripts/check-lab-apply-tooling-preflight.sh

```



### Rule



Tooling readiness is not apply permission.



No SQL is applied in v9.9.1.



---



## v9.9.2 — DB URL Safe Preflight



This checkpoint adds safe `SUPABASE_DB_URL` preflight checks before any future lab-only SQL apply attempt.



### Command



```bash

./scripts/check-supabase-db-url-preflight.sh

```



### Rule



The DB URL is secret.



The system may check its shape and connection readiness without printing the value.



No SQL is applied in v9.9.2.



---



## v10.0.0 — Supabase Lab First SQL Apply



This checkpoint records the first guarded Supabase Lab SQL apply.



### Boundary



Lab-only.



Production remains blocked.



No billing, checkout, webhook, subscription enforcement, or paid runtime is activated.



### Verified



10 prefixed Finance Engine lab tables were verified after apply.



---



## v10.0.1 — Post-Apply Seal and Safety Evidence



This checkpoint seals the v10.0.0 first Supabase Lab SQL apply evidence.



### Rule



v10.0.1 does not apply SQL.



It records and verifies the post-apply safety boundary:



- production remains blocked

- billing remains blocked

- checkout remains blocked

- webhooks remain blocked

- paid runtime remains blocked

- DB URL and service secrets are not stored



---



## v10.1.0 — Supabase Lab Read-Only Runtime Wiring Gate



This checkpoint defines the first safe runtime wiring gate after the Supabase Lab apply.



### Rule



The first runtime layer may look.



It may not touch.



Mutation, production runtime, billing, checkout, webhooks, and paid runtime remain blocked.



---



## v10.2.0 — Supabase Lab Read-Only Runtime Adapter Skeleton



This checkpoint adds the first read-only runtime adapter skeleton after the v10.1.0 gate.



### Rule



The adapter skeleton can prepare read-only query plans.



It cannot connect, execute, mutate, or activate production runtime.



---



## v11.0.0 — Read-Only Runtime Foundation Lock



This checkpoint locks the read-only runtime foundation after the v10.3.0 → v10.9.0 master line.



### Rule



The system now has eyes.



The hands remain locked.



No database execution, mutation, production runtime, billing, checkout, webhooks, or paid runtime is activated.



---



## v12.0.0 — Server-Side Read-Only Executor Candidate Lock



Executor candidate locked.



Execution still requires a separate activation gate.



Canonical domain: `finance.andyai.ai`



---



## v13.0.0 — Finance Engine Online Proof Lock



Online proof surface locked for `finance.andyai.ai`.



Routes:



- `/finance-proof`

- `/api/finance/read-only/status`



The system now has eyes.



The hands remain locked.



---



## v13.9.0 — Prestige Product Index



AndyAI Finance Engine is now presented as a governed financial modeling product surface.



Public proof routes:



- `https://finance.andyai.ai/`

- `https://finance.andyai.ai/finance-proof`

- `https://finance.andyai.ai/api/finance/read-only/status`



Core boundary:



> The system now has eyes. The hands remain locked.



See:



- `docs/product/README_PRESTIGE_INDEX_v13.9.0.md`

- `docs/tutorials/CLIENT_EXPLANATION_STARTER_v13.9.0.md`



---



## Current Product Milestones



- v100.0.0 — Product Value Proof locked

- v110.0.0 — Client Conversion and Pilot Readiness line



## Current Public Positioning



AndyAI Finance Engine turns messy financial documents into a reviewable model package with assumptions, evidence, risk notes, and human approval before anything is used.



## Pilot CTA



Request a pilot run — no payment, no automation, human review included.