Topolo Forecast
Cash-flow and P&L forecasting product.
Documentation Map
What It Is
Cash-flow and P&L forecasting product.
Architecture
Owners: finance-platform
Source repos:
Dependencies: topolo-auth, topolo-one, applications-packages
Repo shape
No repo surface entries were detected from the registered repo paths.
Runtime Surfaces
Hosts:
https://forecast.topolo.app https://forecast-api.stg.topolo.us https://forecast.stg.topolo.us No wrangler surface was discovered under the registered repo paths.
API Reference
Coverage: curated
Source: PlatformApplications/TopoloDocs/src/content/public/applications/forecast.mdx
Source exists in repo: no
Canonical Forecast coverage now lives in the docs application. Forecast resolves the concrete Auth service id for `topolo-forecast` at runtime through Auth `/api/services/by-slug/topolo-forecast`; source and browser bundles must not carry environment-specific `svc_*` or `srv_*` ids. The browser callback delegates Auth SSO one-time sso_code redemption to the shared Topolo auth client and does not support direct bearer-token callback URLs or /sso?token= bridge routes. Embedded first-party password-login success is completed by Forecast with in-app navigation after shared Auth token persistence so the first authenticated workspace refresh is not aborted by a hard redirect. Forecast keeps same-tab sessionStorage access-token restore enabled by default after login and refresh so normal browser reloads do not appear logged out before cookie refresh completes. The authenticated Forecast web workspace renders through the shared `TopoloAppShell` so account, launcher, command, theme, sidebar-collapse, and account-menu BugFix chrome stay package-owned while finance workspace switching remains in additive account-menu actions. Public landing, login, callback, and shared-workspace routes do not mount standalone BugFix controls. Auth home-path redirects to /dashboard are routed to the current-year dashboard in the browser, and Forecast static headers must not preload wildcard asset paths. Worker bearer-token authentication now requires Topolo Auth /validate and does not accept an app-local JWT secret.
App API page: /reference/apps/topolo-forecast
This system currently relies on a curated or README-derived contract surface instead of a source-controlled OpenAPI spec.
Auth and Permissions
Depends on Topolo Auth: yes
Service IDs:
srv_T0sKE7LIelMU API key scopes
Manage Forecast machine credentials
Resource pattern: none
View financial dashboard
Resource pattern: none
View cashflow forecasts
Resource pattern: none
Create and edit forecasts
Resource pattern: none
View financial reports
Resource pattern: none
View account settings
Resource pattern: none
Manage account configuration
Resource pattern: none
View financial transactions
Resource pattern: none
Record financial transactions
Resource pattern: none
Service permissions
api_keys:write, dashboard:read, forecasts:read, forecasts:write, reports:read, settings:read, settings:write, transactions:read, transactions:write
Data Ownership
No storage bindings were derived from wrangler configuration.
Queues / Cron / Workflows
Queue bindings:
No queue bindings were detected.
Cron triggers
No cron triggers were detected.
Workflow signals
No explicit queue/workflow script or cron signal was discovered.
Environment Variables and Bindings
Environment variables:
No environment variables were derived from wrangler configuration.
All wrangler bindings
No bindings were derived from wrangler configuration.
Deployments
Deployment environments: default only or not declared
Routes: workers.dev or Pages-only delivery
Observability enabled: no explicit setting found
Failure Modes
- No wrangler.toml surface was discovered under the registered repo paths.
- The registered contract source is missing: PlatformApplications/TopoloDocs/src/content/public/applications/forecast.mdx
- Neither OpenAPI nor README-derived interface detail was found.
Debugging Runbooks
Start with these entrypoints:
- PlatformApplications/TopoloDocs/src/content/public/applications/forecast.mdx
Change Log / Verification
Lifecycle: active
Last verified: 2026-05-14
Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.