git-subtree-dir: .stage-pilot git-subtree-split: 2c0510c68add43c50adcdedb30c174e68e730395
3.2 KiB
3.2 KiB
Sample Output: bootstrap-baseline
- Input:
- fresh host repository after StagePilot install
- Asked Questions:
project-summary->Python-based API service for curated market data analysisprimary-domain->financial analyticstech-stack->Python, FastAPI, PostgreSQLprimary-runtime->api-serviceprimary-entrypoints->uvicorn src.main:app :: serve the HTTP API,python -m src.jobs.refresh_market_data :: refresh curated market data snapshotsinterface-contracts->HTTP market data API :: http-api :: internal dashboards and downstream service clients :: serve curated market data and derived analytics to clients,Refresh job command :: cli :: operators and scheduled automation :: update stored market data snapshots from upstream sourcesinterface-inputs->HTTP market data API :: GET /markets/{symbol} :: request the current curated snapshot for a symbol,HTTP market data API :: GET /analytics/{symbol} :: request derived analytics for a symbol,Refresh job command :: python -m src.jobs.refresh_market_data :: trigger a refresh of curated market data snapshotsinterface-outputs->HTTP market data API :: JSON market snapshot payload :: current normalized market data for the requested symbol,HTTP market data API :: JSON analytics payload :: derived analytics and summary metrics for the requested symbol,Refresh job command :: refreshed local snapshot artifacts :: normalized data persisted for later API readsinterface-errors->HTTP market data API :: 404 not_found :: symbol is not available in the curated dataset,HTTP market data API :: 503 upstream_unavailable :: refreshed data is temporarily unavailable,Refresh job command :: non-zero exit code :: refresh failed and data should be treated as stalecore-entities->Market Snapshot :: represent the latest curated market data for a tracked symbol,Analytics Snapshot :: represent derived metrics computed from a market snapshotpersistence-backend->PostgreSQLcompatibility-rules->HTTP market data API :: response payload changes should remain backward compatible within the same API version,Refresh job command :: command arguments and exit-code semantics should remain stable for automation callers
- Created Files:
.stage-pilot/bootstrap/baseline.yamldocs/discovery/index.mddocs/srs/index.mddocs/batches/index.mddocs/releases/index.mddocs/project-structure.mddocs/runtime-flows.mddocs/interface-contract.mddocs/data-model.md
- Seed Status:
.stage-pilot/bootstrap/baseline.yaml: created
- Baseline Status:
docs/project-structure.md: createddocs/runtime-flows.md: createddocs/interface-contract.md: createddocs/data-model.md: created
- Index Status:
docs/discovery/index.md: createddocs/srs/index.md: createddocs/batches/index.md: createddocs/releases/index.md: created
- Notes:
- baseline docs were rendered from
.stage-pilot/bootstrap/baseline.yaml - no Discovery document was created
- no REQ, Batch, or Release unit was opened
- baseline docs were rendered from
- Next Action:
/new-discovery <actual product or service change topic>