Repository navigation
feat(core): implement persistent platform and supervised Harness - #7
Merged
Merged
Conversation
github-actions
Bot
added
documentation
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
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.
Adds the first application core behind platform-owned research contracts: SQLite records and ordered events, immutable report bytes, archive integrity, validated human interactions, idempotent run creation, cancellation and restart reconciliation. A generic sequential Harness runs in a supervised IPC child with replaceable model/tool/context interfaces.
Validation: native Windows Node.js 24.19.0, strict TypeScript, Markdown/repository checks, 28 tests, diff whitespace checks and Gitleaks passed. Two opt-in DeepSeek Flash calls passed Chinese streaming and structured tool calling with reported usage. No credentials enter source or archives.
The browser workspace, retrieval, generic skill installation and full literature acceptance remain subsequent iterations, recorded in docs/implementation-plan.md.