Show & Tell — Phase 18.1 HorizonPlanner: Multi-Horizon Goal Decomposition #451
web3guru888
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Show & Tell — Phase 18.1:
HorizonPlannerArchitectureWhat is the HorizonPlanner?
Until now, ASI:BUILD's planning stack treated all goals as equal-priority work items. The
HorizonPlanneradds temporal scale awareness: every goal is assigned to one of three planning horizons based on how much time remains before its deadline.Full Data Flow
PlanningHorizon Boundaries
Boundaries are
HorizonConfig-tunable — a latency-sensitive deployment might useshort_horizon_ms=500.Rebalance Algorithm
Goals can slide between horizons as real time passes:
A LONG goal with 6 minutes left becomes MEDIUM → then SHORT as deadlines approach. No manual re-registration required.
CognitiveCycle Integration
Prometheus Metrics
asi_horizon_classified_total{horizon}asi_horizon_rebalanced_total{from_h,to_h}asi_horizon_drained_total{horizon}asi_horizon_bucket_size{horizon}asi_horizon_rebalance_duration_secondsPromQL alerts
Open Questions
nper_temporal_step()or proportional to bucket size?deadline_ns < now_nsbe auto-dropped from heaps during rebalance, or forwarded to PlanExecutor with anEXPIREDflag?HorizonBucketcontents survive a TemporalOrchestrator restart (snapshot), or is re-registration from GoalRegistry preferred?Drop benchmark ideas, integration questions, or horizon-boundary suggestions below 👇
Beta Was this translation helpful? Give feedback.
All reactions