Statement generation, geographic board inclusion, SDK/CauseStarter fold - #141
Merged
Conversation
Capture the process, cause-assist guidance, and exercise-1 OSS/local-food planks (earmark grain, geographic parents) so a later session can mass-seed without hand-wordsmithing. Not yet in live seed-content.
Accepted OSS and local-food planks now live in seed-content/simple-causes.json. Tiny-seed garden alignment is unchanged. Live Grey→Ontario checks are scripted; the farmers-market Ontario parent dropped "more" only as a workaround. Nested-place boards vs the attester (container vs throughout) is still Ask: do not copy that workaround, somewhere-in, or an any-over-counties combinator.
Stop teaching Grey→Ontario as a designed-yes implication in statement generation, cause-assist, and seed gold. Ontario-wide planks stay as genuine wants; the garden seed publishes a Grey County relevant area and the local-food roster scopes within Ontario.
Canonical cutoff wording now contains the 12-16 week deal on the modified-right (patterns page, bridge-creator, exercise JSON). Live attester blesses both modifieds and refuses both naturals. Not loaded into seed-content.
Production defaults live in PRODUCTION_OPENROUTER_MODEL; laptop scripts use a separate DEV_OPENROUTER_MODEL path so they can diverge later. Cause-assist now prefers OpenRouter over xAI when both keys are set.
CauseStarter now reads the same config.json-backed machinery as the rest of the SPA, so IPFS overlays apply. Delete the CS copies of runtime config, wagmi helpers, and WalletButton; route through domain manifests and barrels.
Move Hardhat keys, fake CIDs, and mock IPFS to @commonality/sdk/testing, let createWriteClients take a chain, and compile only src plus ABIs. Retire the unused schema/codegen path.
The attester prompt no longer treats Grey County → Ontario as an accept rule. Resume-aware generation retries empty LLM responses and re-evaluates stale prompt fingerprints. The checked-in seed implication corpus is unchanged and still needs a live refresh.
Break the 1300-line name-scan decoder into per-subsystem modules and pass the contract ABI into decodeEventLog so shared event names cannot pick the wrong ABI. Keep the public utils re-export. Slice F still has other files.
Conceptspace and content-funding queries stay on the same public barrels; conceptspace event-cache reads page through fetchEventsComplete instead of treating a 10k cap as a complete set.
Keep publishBridgeCluster and page helpers as a real seam. Leave editor and published-view JSX on the page. Slice G is stale-path nits already covered elsewhere or marked opportunistic, so the plan is no longer useful.
Do not treat missing project metadata as a geographic miss (content-funding and in-flight IPFS reads), key aligned-list snapshots by inclusion rules, restore Compose env interpolation for cause-assist models, and pair an explicit xAI base URL with the xAI key.
AdamSpitz
commented
Aug 27, 2026
AdamSpitz
left a comment
AdamSpitz
left a comment
Owner
Author
There was a problem hiding this comment.
Review receipt.
Reviewed statement-generation-process vs origin/dev. Geographic-filter bugs (missing metadata treated as a miss; unkeyed list snapshots), Compose model pinning, and xAI/OpenRouter key mix were fixed on this head. Remaining work is already on TODO (seed implication re-eval, exercise-2 Ask, CauseStarter path sweep). No open findings on 275f15e.
Reviewed-with: grok
Reviewed-files: 329
Reviewed-commit: 275f15e
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Statement-generation process plus the related product and platform work that landed on this branch:
seed-content/).relevantAreas/ Worldwide, and the attester prompt rejects geographic rollup as implication.causestarter/srcSPA glue is a known Tell follow-up.deepseek/deepseek-v4-flash-0731.Known follow-ups (already in TODO)
data/seed-implication-evaluations.original-variants.jsonagainst the current implication-attester fingerprint (test:seed:implication-regressionwill fail until a live re-eval)./critique-triple, Adam accept/reject before seed.Review notes
Branch review vs
origin/dev(329 files). Bugs above were fixed in the last commit. Remaining items were suggestions/nits, now addressed or already tracked.Test plan
test:fast/code-review --comment+scripts/post-review.sh(requiredreview-received)CAUSE_ASSIST_SUGGEST_MODELin.envoverrides the DeepSeek default