feat: give GOFAI structured actions and goal-directed planning #1343

Timmy · 2026-04-13T01:29:42Z

Timmy commented

2026-04-13 01:29:42 +00:00

Summary

upgrades the off-thread GOFAI worker from generic matches to structured symbolic action objects
derives the planning goal from the current symbolic pressure instead of always aiming at a fixed stability target
adds a second planner action, Shed Portal Load, so critical-drain states have a symbolic response path

Why this matters

before this PR, the worker always returned OFF-THREAD MATCH, even when the symbolic system already knew the concrete intended response
planning also always targeted { stability: 1.0 }, which ignored the distinct CRITICAL_DRAIN_PATTERN case
after this PR, GOFAI can distinguish between:
- stabilization pressure -> goal { stability: 1.0 }
- drain pressure -> goal { activePortals: 0, stability: 0.8 }
the worker now returns structured off-thread reasoning payloads with:
- outcome
- triggerFacts
- confidence

Verification

failing-first synthetic verification before implementation showed all target behaviors missing
passing verification after implementation:
- node /tmp/verify_gofai_structured_actions.js
- node /tmp/verify_gofai_live_perception.js
syntax checks:
- node --check app.js
- node --check gofai_worker.js
diff budget check against main:
- additions=10, deletions=3, net=7
repo_truth_guard.py still fails, but a clean origin/main worktree reproduces the same baseline failure (Dockerfile missing Python dependency: websockets/playwright), so this PR does not introduce that red state

Summary - upgrades the off-thread GOFAI worker from generic matches to structured symbolic action objects - derives the planning goal from the current symbolic pressure instead of always aiming at a fixed stability target - adds a second planner action, `Shed Portal Load`, so critical-drain states have a symbolic response path Why this matters - before this PR, the worker always returned `OFF-THREAD MATCH`, even when the symbolic system already knew the concrete intended response - planning also always targeted `{ stability: 1.0 }`, which ignored the distinct `CRITICAL_DRAIN_PATTERN` case - after this PR, GOFAI can distinguish between: - stabilization pressure -> goal `{ stability: 1.0 }` - drain pressure -> goal `{ activePortals: 0, stability: 0.8 }` - the worker now returns structured off-thread reasoning payloads with: - `outcome` - `triggerFacts` - `confidence` Verification - failing-first synthetic verification before implementation showed all target behaviors missing - passing verification after implementation: - `node /tmp/verify_gofai_structured_actions.js` - `node /tmp/verify_gofai_live_perception.js` - syntax checks: - `node --check app.js` - `node --check gofai_worker.js` - diff budget check against main: - additions=10, deletions=3, net=7 - `repo_truth_guard.py` still fails, but a clean origin/main worktree reproduces the same baseline failure (`Dockerfile missing Python dependency: websockets/playwright`), so this PR does not introduce that red state

Timmy added 1 commit 2026-04-13 01:29:43 +00:00

feat: give GOFAI worker structured actions and live goals

CI / test (pull_request) Failing after 24s

Details

CI / validate (pull_request) Failing after 16s

Details

Review Approval Gate / verify-review (pull_request) Failing after 2s

Details

770ed8c27a

Timmy requested review from perplexity 2026-04-13 01:29:45 +00:00

Timmy merged commit 71e8ee5615 into main

2026-04-13 01:34:47 +00:00

Timmy referenced this issue from a commit

2026-04-13 01:34:49 +00:00

Merge PR #1343

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Timmy_Foundation/the-nexus#1343