chore: keep the public repo to project content; align LITEPAPER with the pitch

.gitignore

@@ -82,18 +82,9 @@ KumplyMainnet.md
 /.windsurfrules
 /.agents/
 
-# Internal agent skills and playbooks - kept locally and in kumplyprotocol/internal (private),
-# not in the public repo. Removed from tracking 30-Sep-2026; history not rewritten.
-/.claude/skills/teammate-commit-identity/
-/.claude/skills/full-context-loading/
-/.claude/skills/mexico-legal-check/
-/.claude/skills/grants-track-record/
-/.claude/skills/portfolio-funding-rollup/
-/.claude/skills/hackathon-fit-check/
-/.claude/skills/doc-accuracy-audit/
-/.claude/skills/public-claim-verify/
-/.claude/skills/repo-security-sweep/
-/.claude/skills/avalanche/
-/.claude/skills/claude-antigravity-setup/
-/PLAYBOOK-claude-antigravity-setup.md
+# Local agent tooling (not part of the project)
+/.claude/skills/
+/.claude/commands/
+/playbooks/
+/PLAYBOOK-*.md
 /skills-lock.json

AGENTS.md

@@ -2,31 +2,20 @@
 
 This file carries the hard rules that apply to any AI agent working in this
 repo, regardless of tool (Claude Code, Antigravity, Cursor, etc.). It is
-public and safe to read by anyone — internal strategy, team, and grant
-context live in `CLAUDE.md` / `claude_estrategico.md` / `Memory.md`, which
-are gitignored on purpose (see "Public/private boundary" below) and never
-duplicated here.
+public and safe to read by anyone.
 
 For architecture, contracts, and full technical detail, start with
 [README.md](README.md) and [LITEPAPER.md](LITEPAPER.md), not this file —
 this is rules, not documentation.
 
 ## Public/private boundary
 
-`CLAUDE.md`, `claude_estrategico.md`, `Memory.md`, `.agents/`,
-`.cursorrules`/`.windsurfrules`/`.clinerules`, and `docs/submissions/` are
-intentionally excluded from this public repo (see `.gitignore`). They hold
-internal strategy, team contacts, and grant-negotiation context; copies sync
-manually to a private repo. Never move content from those files into this
-one or into any other public file — if something in them needs to be public,
-it gets rewritten for a public audience first (see `docs/AI-USAGE.md` and
-the README's "Security & Engineering Rigor" section for the pattern already
-used).
-
-Internal agent skills and playbooks (for example `mexico-legal-check` and
-`teammate-commit-identity`) are gitignored here. Copies live in
-`kumplyprotocol/internal` under `ai-rules/skills/` and `playbooks/`. Don't
-add them back to this repo.
+Local agent files (`CLAUDE.md`, editor rule files, root `.claude/skills/`
+and `.claude/commands/`, `playbooks/`) and internal planning notes are
+gitignored on purpose and kept outside this repo. Never copy content from
+them into a tracked file. If something there needs to be public, rewrite it
+for a public audience first (see `docs/AI-USAGE.md` and the README's
+"Security & Engineering Rigor" section for the pattern already used).
 
 ## Solidity
 
@@ -134,45 +123,19 @@ add them back to this repo.
   already-deployed and verified contract get reported and confirmed by a
   human before being applied — not applied automatically.
 
-## Session resumption and hallucination discipline
+## Accuracy
 
-**When resuming with `claude --continue`, don't re-read what's already
-in context or re-verify what's already verified this session.** Answer
-directly on what's already established. Detail and why in
-`playbooks/continue.md`.
-
-**Zero hallucination. Anything date-dependent gets verified live before
-being stated, never from training memory — versions, prices, platform
-rules, legal deadlines.** It's fine to say "I don't know, that needs
-verifying." Every claim should trace back to something verifiable; if
-not, mark it as inference. Full guidance in `playbooks/continue.md`.
-
-## Images and screenshots
-
-**Image token cost is area-based, not file-weight-based — crop to the
-relevant region before pasting.** Compressing the file (JPEG/WebP)
-doesn't reduce tokens and can hurt text legibility; cropping dimensions
-does. Detail and verified figures in `playbooks/images.md`.
-
-**Batch multiple images into the same turn instead of pasting them one
-at a time across separate turns.** Each new image invalidates the
-prompt cache from that point forward — pasting one at a time forces
-repeated cache rewrites instead of cheap reads. Detail in
-`playbooks/images.md`.
+- Anything date-dependent (versions, prices, platform rules, legal
+  deadlines) is verified live before it is stated, never from memory.
+  If it can't be verified, say so or mark it as inference.
 
 ## Writing PRs, issues, and comments on GitHub
 
-**Every PR, issue, and comment published to GitHub is written humanized
-and tight - no padding, no AI-writing tells (em dashes, curly quotes,
-unicode ellipsis), and the Co-Authored-By disclosure stays visible,
-never stripped out to look more human.** Detail in `playbooks/git.md`.
-
-**When the root cause is already confirmed, propose the actual fix, not
-just the report.** A diff, corrected line, or exact reproduction beats
-"this seems broken." Detail in `playbooks/git.md`.
-
-**When citing or paraphrasing another thread, re-read the actual source
-today before writing the citation - the disclosure's re-verification
-sentence is only added if that re-read really happened.** A short, true
-disclosure beats a longer one nothing backs up. Detail in
-`playbooks/git.md`.
+- Tight and specific: state the finding, the evidence, and what was done.
+  No padding.
+- The AI-assistance disclosure stays visible on every PR and comment that
+  had AI help. It is never removed.
+- When the root cause is confirmed, include the fix (a diff or the
+  corrected line), not just the report.
+- When citing another thread, re-read the source the same day before
+  quoting it.

LITEPAPER.md

@@ -160,16 +160,18 @@ This unlocks **agentic DeFi with safety rails**: an autonomous market-making bot
 
 ## 5. Business Model - Software-Only, B2B
 
-KUMPLY operates as **infrastructure software**, not a financial institution. We do not custody funds, do not facilitate fiat/crypto exchange, do not issue tradable assets. Revenue comes from:
+KUMPLY operates as **infrastructure software**, not a financial institution. We do not custody funds, do not facilitate fiat/crypto exchange, do not issue tradable assets.
 
-| Stream | Customer | Pricing | Channel |
+**Free reads. Verification is the product.** Integrators call `verify()` for free, with no subscription, on Fuji and Mainnet C-Chain. It is a view function that never touches the fee settings, so reads are free by contract design, not only by policy. Revenue sits on the issuance side:
+
+| Stream | Customer | Pricing | Status |
 |---|---|---|---|
-| **SaaS subscription** | Regulated institutions (banks, enterprises) | MXN/USD monthly fixed (CFDI billing) | Direct sales |
-| **Pay-per-use API** | DApps, autonomous agents, small teams | $0.50 USD per `checkCompliance` call, paid in AVAX | Smart contract |
-| **L1 gas (KMP)** | Validators, DApps deploying on KUMPLY L1 | Native gas fees on L1 transactions | On-chain |
-| **Verifier-as-a-Service** | KYC providers wanting on-chain distribution | License + revenue share | Partnership |
+| **Issuance fee** | Businesses (Tier 4, KYB) and agent owners (Tier 5, KYA) | Fee per verified business or agent, paid by the owner, covering the identity-provider check and review | Planned for M3. No fee is active today |
+| **Service plans** | Integrators that depend on KUMPLY in production | Optional: support and response times, priority issuance for their users, revocation alerts. Billed off-chain; nothing in the contracts gates reads | Planned |
+| **L1 gas (KMP)** | DApps deploying on the KUMPLY L1 | Native gas fees on L1 transactions | Planned, after L1 activation |
+| **Verifier-as-a-Service** | KYC providers wanting on-chain distribution | License + revenue share | Planned |
 
-Pricing benchmark: traditional KYC providers (Sumsub, Onfido, Veriff) charge $1–8 per verification with no on-chain composability and no programmatic API for smart contracts. Our $0.50 per-check is a 50–94% cost reduction, plus the compliance data is reusable across every Avalanche DApp the user touches - meaning per-user lifetime cost trends toward zero as the network effect compounds.
+Why issuance and not reads: the identity-provider check is the real cost, and it happens once. After that, the attestation is readable by every Avalanche DApp the user touches at no charge, so no integrator pays again for a check that was already done.
 
 ## 6. Token: KMP
 
@@ -203,28 +205,28 @@ The weakest part of this project is unproven demand (§1.1), so closing it is th
 
 **Deliverable:** a published findings document with attributable quotes, and either (a) 2 confirmed pilot integrators - Avalanche builders or startups willing to test `ComplianceGate` or the SDK, KUMPLY's actual near-term buyer, not necessarily a regulated institution - or (b) a documented decision to re-target the ideal customer profile. Outcome (b) is a valid result, not a failure - it is cheaper to learn it in week two than in month six. Outcome (a)'s integrators are the candidates for M4's pilot integrations - the demand-validation and proof-of-concept work share one pipeline, not two.
 
-**Status:** M0 is already producing signal, not just plans. One candidate integrator is in active conversation, with an expected close date within the next two weeks - not signed yet. A separate early conversation closed with a clear "not yet": no real funds at stake today, revisit once third parties can publish paid agents on the platform. That answer is itself real-time M0 evidence, not a setback.
+**Status (October 2026):** M0 is already producing signal, not just plans. A technical pilot with an external infrastructure team ran live on Fuji on Sep 30, 2026 (gas sponsorship gated by KUMPLY attestations, details at [kumply.xyz/pitch](https://kumply.xyz/pitch)). Integration conversations continue; nothing is signed yet. A separate early conversation closed with a clear "not yet": no real funds at stake today, revisit once third parties can publish paid agents on the platform. That answer is itself real-time M0 evidence, not a setback.
 
 ## 8. Team & Traction
 
 - **Two co-founders.** Giovanny Amador - Engineering Lead: smart contracts, L1, SDK and infrastructure (authorship visible in the public commit history); also a hackathon winner outside Avalanche - ETH Uruguay 2025, 1st place at ETH Mexico Monterrey (Creator Economies track), 3rd place Arbitrum Innovation track. Monserrat Mendoza - Dev Lead: frontend UX/UI and backend developer; also a hackathon winner outside Avalanche - ETH Uruguay 2025. Both are Team1 Network Collaborators (accepted July 2026).
 - **Bus factor.** Most shipped code still runs through one founder today (Giovanny - every commit attributable to him, verifiable in the repo's public history). Monse has now shipped a real fix here too (commit `49177e0`, address validation before `readContract`) - a second contributor is real, just not yet at parity.
 - **Code:** monorepo with pnpm workspaces - contracts, SDK, API, web - full test suite (contracts, SDK, API), CI on every push (GitHub Actions, 4 parallel jobs).
-- **Go-to-market:** targeting Mexican digital banks, venture funds and LatAm enterprises. No commercial agreements are signed to date; any partner will be named only once a relationship is formalized.
+- **Go-to-market:** targeting Mexican digital banks, venture funds and LatAm enterprises. No commercial agreements are signed to date; a partner is named only with their written permission.
 - **Open source:** Apache 2.0 licensed (express patent grant, no trademark license), public GitHub, no proprietary lock-in.
-- **Public commitment:** all smart contracts will be immutably renounced to a 3-of-5 multisig before mainnet; KMP mainnet genesis defined by community governance; quarterly treasury transparency reports starting Q4 2026.
+- **Public commitment:** admin roles on the deployed contracts move to a 3-of-5 multisig before any fee is activated on Mainnet C-Chain (part of M3's cold-key treasury); KMP mainnet genesis defined by community governance; quarterly treasury transparency reports starting Q4 2026.
 
 ## 9. Grant Programs & Funding Asks
 
 We are applying to:
 
 | Program | Amount | Use of funds |
 |---|---|---|
-| **Team1 Mini-Grant** | $10,000 USD, modular | Five milestones, fundable in tranches: **M0 ($0)** demand validation - 5 structured interviews with published findings, runs regardless of funding and is not a disbursement gate (§7.1) · **M1 ($2,000)** security hardening of `AttestationStore` + `ComplianceGate` (Slither, Aderyn, fuzzing, threat model) plus failure detection and alerting on the issuance path · **M2 ($3,000)** Mexican legal entity incorporated (a hard prerequisite for Sumsub's production tier), Sumsub production activated, first real KYC on-chain - includes a ring-fenced reserve against the pending Enterprise quote for Tier-4 KYB · **M3 ($2,000)** on-chain query-fee activation on Mainnet C-Chain, written Mexican fintech legal opinion, IMPI trademark, cold-key treasury · **M4 ($3,000)** Fuji L1 validator activation, ICM integration, 2 integration pilots. $5,000 funds M1–M2; $7,000 adds M3; $10,000 completes M4. Excludes formal L1 audit. Full itemisation at [kumply.xyz/pitch](https://kumply.xyz/pitch). |
+| **Team1 Mini-Grant** | $10,000 USD, modular | Five milestones, fundable in tranches: **M0 ($0)** demand validation - 5 structured interviews with published findings, runs regardless of funding and is not a disbursement gate (§7.1) · **M1 ($2,000)** security hardening of `AttestationStore` + `ComplianceGate` (Slither, Aderyn, fuzzing, threat model) plus failure detection and alerting on the issuance path · **M2 ($3,000)** Mexican legal entity incorporated (a hard prerequisite for Sumsub's production tier), Sumsub production activated, first real KYC on-chain - includes a ring-fenced reserve against the pending Enterprise quote for Tier-4 KYB · **M3 ($2,000)** issuance fee activation on Mainnet C-Chain (reads stay free), written Mexican fintech legal opinion, IMPI trademark, cold-key treasury · **M4 ($3,000)** Fuji L1 validator activation, ICM integration, 2 integration pilots. $5,000 funds M1–M2; $7,000 adds M3; $10,000 completes M4. Excludes formal L1 audit. Full itemisation at [kumply.xyz/pitch](https://kumply.xyz/pitch). |
 | **Avalanche Retro9000** (C-Chain, future round) | Retroactive | Bringing KUMPLY to mainnet as compliance infrastructure: institutional validator-set bootstrap and formal smart-contract audit |
 | **Blizzard Fund** | Seed round, terms TBD | Operating runway 12 months (legal, audits, BD) and engineering hires |
 
-Capital efficiency is core: at $0.50 per-check pricing, breakeven on operating costs is reached at ~50K monthly verifications - a single mid-size LatAm enterprise customer.
+Capital efficiency is core: reads are view calls that any Avalanche RPC serves, so KUMPLY's operating cost scales with issuance, which is also where revenue sits.
 
 ## 10. Why We Win
 

SETUP.md

@@ -30,9 +30,9 @@ cd ..
 ```
 
 Both `.claude/skills/avalanche-skills/` and `.reference/` are gitignored (see `.gitignore`,
-"Avalanche reference tooling" section). The gitignore entry is scoped specifically to
-`avalanche-skills/`, not all of `.claude/skills/`, so it never hides any of KUMPLY's own skills
-if some get added there later.
+"Avalanche reference tooling" section). Everything under the root `.claude/skills/` is local
+tooling and stays out of the repo. KUMPLY's own project skill, `run-web`, lives under
+`apps/web/.claude/skills/` and is tracked.
 
 None of this is committed to the public repo, under any circumstance:
 - `avalanche-starter-kit` ships with no `LICENSE` file at all.

docs/audits/avalanche-ecosystem-audit-2026-08-17.md

@@ -157,19 +157,16 @@ Reporting this plainly rather than inventing an item to fill the category.
 
 ## Add - flagged, not applied
 
-### 5. Gas optimization vs Retro9000
+### 5. Gas optimization
 
 `skills/gas` and `skills/precompiles` list standard storage-packing, calldata, and unchecked-loop
 optimizations. AttestationStore, ComplianceGate, and KumplyValidatorSetManager already follow the
 main patterns those skills recommend: custom errors instead of require strings, calldata for
 external function inputs, events over storage-based history, checked arithmetic outside of
-explicitly bounded loops. No unsafe or clearly-missed optimization was found.
+explicitly bounded loops. No unsafe or clearly-missed optimization was found, so no gas changes
+were made in this pass.
 
-Flagging the tension explicitly, as asked: KUMPLY intends to apply to Retro9000, which rewards
-AVAX burned via gas on Mainnet C-Chain. Reducing gas per call directly reduces that metric. Any
-future gas optimization pass on these contracts should be a deliberate business decision made
-with that trade-off in view, not a default "smaller is better" pass. Not applying anything gas
-related here for that reason, beyond what was already true before this audit.
+*(Section 5 edited 8 Oct 2026 for scope: it now records only the technical finding.)*
 
 ### 6. ReentrancyGuard on AttestationStore.withdrawFees
 
@@ -245,7 +242,7 @@ https://github.com/Ayomisco/avaxskills/issues/2
 | 2 | Fix | contracts/contracts/KumplyValidatorSetManager.sol | Medium | Fixed in same redeploy |
 | 3 | Fix | apps/web/src/app/api/webhook/route.ts, apps/api/src/index.ts | Medium | Fixed |
 | 4 | Improve | contracts/scripts/verify-contracts.ts | N/A | Applied |
-| 5 | Add | gas optimization | N/A | Flagged, not applied (Retro9000 trade-off) |
+| 5 | Add | gas optimization | N/A | Reviewed, no missed optimization found |
 | 6 | Add | contracts/contracts/AttestationStore.sol | Low | Reported, needs confirmation |
 | 7 | External (upstream) | AVAXSKILLS skills/precompiles | N/A | Filed, avaxskills#3, open |
 | 8 | External (upstream) | AVAXSKILLS skills/validator-management | N/A | Filed as comment on avaxskills#2, open |