Skip to content

Run shadow signal workflow monthly #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Pigbibi merged 1 commit into from
May 28, 2026
Merged

Run shadow signal workflow monthly #8

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/dispatch_shadow_signal.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,9 @@ name: Long Horizon Shadow Signal

on:
schedule:
# Weekly after Friday US market close. This remains shadow-only and does not
# place trades.
- cron: "30 2 * * 6"
# Monthly shadow research run. This remains shadow-only and does not place
# trades.
- cron: "30 2 1 * *"
workflow_dispatch:
inputs:
provider:
Expand Down
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ point-in-time artifact is `data/output/signal_history/2026-05-28.json`.

Near-term work should focus on:

- keeping the weekly workflow healthy
- keeping the monthly workflow healthy
- accumulating saved `signal_history/*.json` artifacts
- replaying only saved artifacts, not regenerated historical AI judgments
- improving context quality before any downstream plugin integration
Expand All @@ -65,7 +65,7 @@ plugin contract.

## Operating Model

1. A weekly workflow builds a point-in-time context bundle from current market
1. A monthly workflow builds a point-in-time context bundle from current market
prices.
2. The workflow creates or updates a dated long-horizon shadow-signal issue and
embeds the context bundle as review evidence.
Expand Down Expand Up @@ -127,7 +127,7 @@ python scripts/build_context_bundle.py \

Without `--prices`, the script downloads recent daily prices for the default
universe through Yahoo's chart endpoint and writes a point-in-time context bundle
for the weekly shadow issue. The scheduled workflow uses
for the monthly shadow issue. The scheduled workflow uses
`--allow-download-errors`, so external data-source failures still create an
operator issue with the failure recorded instead of silently skipping the run.

Expand Down
2 changes: 1 addition & 1 deletion docs/architecture.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ order routing.
- `AiLongHorizonSignalPipelines` stores context examples, schema, validation,
replay tooling, and shadow artifacts.
- `CodexAuditBridge` owns provider routing and API keys.
- GitHub Issues are the first operator notification layer for scheduled shadow
- GitHub Issues are the first operator notification layer for monthly shadow
signal runs.
- The scheduled workflow builds the market context bundle before dispatching the
bridge and embeds that bundle into the issue, because the bridge reads the
Expand Down