Finance Management

Capabilities

Finance is the staff console (Finance Management). Owners without a staff role see Access Required. Your own revenue is Business → Revenue. What you spent is Audit. The owner map is Hub → Money.

• Dashboard / Streams / Credit Economy / Plan lab — staff books

• Referrals, Partner Ops, Stripe Connect, Team/Payroll

• Crypto Assets / Expenses — treasury; Reports is admin-only

What is Finance?

Finance (/finance) is the staff console — Finance Management. Sidebar: Dashboard, Streams, Credit Economy, Plan lab, Referrals, Partner Ops, Stripe Connect, Team/Payroll, Crypto Assets, Expenses. Admins also see Live Balances, Chart of Accounts, Reports. You need a team, founding, or admin role. Owners without that role see Access Required. That is expected.

What it is not

It is not Pricing (your plan). It is not Gas Station (the pump). It is not Audit (your receipt). It is not Hub → Money (the owner map). It is not Business → Revenue. If you are looking at your own bill, open Audit, Pricing, Hub Money, or Business Revenue — not this page.

Not yet

Route: /finance · Audience: Platform administrators, team/founding roles (tab-gated)

Finance is the operator console for platform economics — credits, treasury, partner ops, referrals ledger, fleet health, and internal scenario labs. Not a small-business bookkeeping tool (see Kontext Business → Revenue for owner-facing money).

Finance (/finance) — platform operator console for credits economy, treasury, Partner Ops, referrals ledger, fleet health, and internal labs. Requires team/founding/admin role — not owner bookkeeping (use Kontext Business → Revenue).

• Wallet, Economy, Financials tabs

• Partner Ops — tiers, overrides, commission events

• Pools/Fleet — frozen canister lifecycle

Route: /finance · Audience: Platform administrators, team/founding roles (tab-gated)

Finance is the operator console for platform economics — credits, treasury, partner ops, referrals ledger, fleet health, and internal scenario labs. Not a small-business bookkeeping tool (see Kontext Business → Revenue for owner-facing money).

Route: /finance · Audience: Platform administrators, team/founding roles (tab-gated)

Finance is the operator console for platform economics — credits, treasury, partner ops, referrals ledger, fleet health, and internal scenario labs. Not a small-business bookkeeping tool (see Kontext Business → Revenue for owner-facing money).

Module tabs & intent

Credit economy visibility

Partner & referral operations

See Partner Program & Referrals — Finance Partner Ops is the admin surface for commission tiers, overrides, and ledger events.

Access model

Restricted tabs require Finance module role. Member-facing billing lives in Profile → Subscription panel (Stripe customer portal visibility).

User journeys

FIN-01. Open the Finance operator console

Path: Module switcher → Finance (or /finance)

You do:

1. Sign in with an account that has Finance module permission (admin, team, or founding role).
2. Open Finance from the module switcher or navigate to /finance.
3. Confirm the unified module header loads without access errors.
4. Scan the tab bar — only tabs your role allows should be visible.
5. Sign in as a standard member without Finance role and confirm /finance is blocked or tabs are hidden.

Result: Authorized operators reach the platform economics console; unauthorized users cannot access restricted tabs.

FIN-02. Manage platform wallet (ICP and cycles)

Path: /finance → Wallet tab

You do:

1. Open /finance with Wallet tab access.
2. Review ICP balance and cycle balance for platform operations.
3. Inspect recent treasury movements or top-up history shown in the panel.
4. Initiate a cycle top-up or ICP transfer if controls are exposed for your role.
5. Record the transaction reference for audit.
6. Refresh and confirm balances reflect the operation.

Result: Platform hosting and canister operations stay funded; operators see live wallet state.

FIN-03. Inspect credit economy metrics

Path: /finance → Economy tab

You do:

1. Open the Economy tab.
2. Review credits issued, credits burned, and aggregate balances across the platform.
3. Drill into transaction-style lines tied to hosting, domains, and AI usage where exposed.
4. Compare daily or weekly burn against issuance trends.
5. Note anomalies (spikes in AI chat burns, hosting debits).
6. Cross-check a sample user handle against Profile credits if investigating a dispute.

Result: Operators understand KTX flow and can trace economy health before changing pricing.

FIN-04. Review treasury and financial roll-ups

Path: /finance → Financials tab

You do:

1. Open the Financials tab (restricted role required).
2. Review Platform Treasury — ICP, cycles, reserve requirements, runway indicators.
3. Scan revenue roll-ups and reserve panels (AI token reserve, Claude API balance if shown).
4. Compare MRR/ARR or subscription revenue summaries when present in your build.
5. Export or screenshot key figures for leadership review if export is available.
6. Flag runway warnings if projected burn exceeds reserves.

Result: Leadership sees consolidated financial health separate from member-facing Profile billing.

FIN-05. Configure partner program defaults

Path: /finance → Partner Ops tab → program settings

You do:

1. Open Partner Ops with partner-admin Finance role.
2. Review default commission tiers and activation rules for the partner program.
3. Adjust tier percentages or thresholds per product policy.
4. Save program defaults.
5. Open the partner leaderboard preview to confirm tier labels match saved defaults.
6. Document the change for partner communications.

Result: New partners inherit consistent commission defaults without per-account manual setup.

FIN-06. Override settings for a specific partner

Path: /finance → Partner Ops → partner record

You do:

1. From Partner Ops, search or select an individual partner account.
2. Review their current tier, activation state, and override flags.
3. Apply a per-partner override (custom commission rate or tier) when contracted.
4. Activate or deactivate partner status per policy.
5. Save and reopen the record to confirm persistence.
6. Notify the partner through normal channels — Finance UI does not send external email by itself.

Result: Strategic partners can have bespoke economics while the global defaults remain unchanged.

FIN-07. Audit partner commission events

Path: /finance → Partner Ops → commission events · leaderboard

You do:

1. Open Partner Ops and navigate to commission events (or ledger view).
2. Filter by date range and partner handle.
3. Match an event row to a referral or conversion source ID when tracing disputes.
4. Open the leaderboard to rank partners by attributed volume or commissions.
5. Export or copy rows needed for payout reconciliation.
6. Escalate mismatches to Referrals tab (FIN-08) if reward tracing is unclear.

Result: Partner payouts are auditable line-by-line before funds leave treasury.

FIN-08. Trace platform referral conversions

Path: /finance → Referrals tab

You do:

1. Open the Referrals tab.
2. Browse platform-wide referral conversion rows.
3. Search by referrer handle, referee, or conversion ID.
4. Follow KTX reward tracing columns to see credited amounts and status.
5. Compare a row against Partner Ops commission events when both apply.
6. Mark or annotate internally if a row needs manual correction (per your ops process).

Result: Referral incentives are transparent; finance can answer "who earned what and when."

FIN-09. Run prompt and quality debug analysis

Path: /finance → Debug / Prompt analysis tab

You do:

1. Open the Debug or Prompt analysis tab (internal role only).
2. Select a date range or experiment batch.
3. Review quality metrics, failure rates, or prompt experiment comparisons.
4. Drill into a sample session ID linked from the panel if available.
5. Correlate spikes with deployment or prompt release dates.
6. Share findings with engineering before changing production prompts.

Result: Internal teams validate AI quality and cost tradeoffs without exposing data to members.

FIN-10. Dispatch platform-wide notifications

Path: /finance → Notifications tab

You do:

1. Open the Notifications tab with dispatch permission.
2. Compose a platform-wide or segmented notification (title, body, target scope per UI).
3. Preview audience size or segment rules if shown.
4. Schedule or send immediately per controls.
5. Confirm success toast or job ID.
6. Verify a test account receives the notification in-product.

Result: Operators can broadcast maintenance, releases, or policy updates from one console.

FIN-11. Manage server pools and fleet health

Path: /finance → Pools / Fleet tab

You do:

1. Open Pools or Fleet management.
2. Review server pair pool inventory and assignment state.
3. Inspect fleet health indicators — frozen canisters, depleted modules, lane status.
4. Run revive or top-up actions on frozen canisters when cycles are restored (per ops playbook).
5. Monitor pair fuel levels tied to Gas Station dispense paths.
6. Document canister IDs escalated to Users/WASM tab (FIN-12) if WASM was removed.

Result: Hosted user infrastructure stays healthy; frozen or depleted canisters are visible before users report login failures.

FIN-12. Administer user canisters and WASM

Path: /finance → Users / WASM tab

You do:

1. Open Users or WASM administration (high-privilege role).
2. Search for a user by handle, principal, or canister ID.
3. Inspect canister status, WASM version, and account bootstrap state.
4. Trigger admin reinstall or bootstrap recovery flows when documented (depleted canister playbook).
5. Confirm Account not initialized cases receive bootstrap before credit grants.
6. Log actions for compliance — destructive ops affect live user data.

Result: Operators recover depleted canisters and align fleet WASM without using browser ingress limits.

FIN-13. Operate system Gas Station metering

Path: /finance → Gas Station (system) tab

You do:

1. Open the Gas Station (system) operator panel (not the member /gas-station wallet UI).
2. Review allowlisted dispense paths and system metering configuration.
3. Inspect dispense history or lane summaries tied to platform pairs.
4. Adjust auto-dispense thresholds only within policy limits shown in UI.
5. Run a controlled dispense test on a staging pair if available.
6. Cross-check results on Pools/Fleet (FIN-11) fuel levels.

Result: Platform-side cycle dispensing stays within operator guardrails; member wallets remain separate.

FIN-14. Import and export Plan Lab scenarios

Path: /finance → Plan Lab tab

You do:

1. Open Plan Lab — the economy control plane for scenario modeling.
2. Review the active scenario bundle (subscription tiers, credit issuance, burn assumptions).
3. Export the current bundle for backup or peer review.
4. Import a candidate bundle from staging after leadership approval.
5. Run subscription scenario labs and compare projected MRR or burn against live Economy tab metrics.
6. Roll back to the prior export if projections are unacceptable.

Result: Pricing and credit policy changes are tested before shipping to all members.

FIN-15. Clean up KRN and discovery orphans

Path: /finance → Index cleanup tab

You do:

1. Open Index cleanup with index-admin Finance role.
2. Run or refresh the orphan scan for stale KRN or discovery index entries.
3. Review listed orphans — confirm each is safe to remove (unpublished listings, deleted communities, etc.).
4. Select rows and execute cleanup per UI batch controls.
5. Re-run the scan to confirm zero or expected remaining orphans.
6. Spot-check affected modules (Marketplace, Network, Communities) for broken links.

Result: Discovery indexes stay consistent; removed entities no longer appear in search or KRN-backed agents.

How it works

Route /finance. Operator console for credits and partner/finance ops — staff-gated in the module switcher.

Benefits

• One console for credit economy and partner/finance operations.

Who it's for

Primary: Kontext team / admins / founding roles. Not: normal builders (module hidden by role filter).