Show HN：StegCore – AI 系統的決策邊界（真實 ≠ 許可）

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

To see all available qualifiers, see our documentation.

Core of StegVerse dev.

Uh oh!

There was an error while loading. Please reload this page.

StegVerse-Labs/StegCore

Folders and files

Latest commit

History

Repository files navigation

StegCore

StegCore decides what actions are permitted, given verified continuity.

StegCore consumes verified continuity output (e.g., from StegID) and answers:

StegCore may also maintain internal state/audit signals about StegVerse nodes
(services, agents, devices) to support orchestration and observability — but it is
not the continuity truth system.

What StegCore does NOT do

StegCore does not:

Continuity receipts and verification belong to StegID.

⚠️ StegCore is not a medical or diagnostic system. It is infrastructure used
for orchestration, security, and observability.

v0.1 Scope (tight)

v0.1 is documentation-first. The authoritative spec lives in /docs:

Code in src/stegcore/ is scaffolding and substrate for future runtimes. It must
eventually conform to the docs (docs win if there is disagreement).

Concepts

Supporting substrate (non-authoritative in v0)

Quickstart (scaffold: node state signals)

This example demonstrates internal state/audit signals only, not permission decisions.

About

Core of StegVerse dev.

Resources

Uh oh!

There was an error while loading. Please reload this page.

Stars

Watchers

Forks

Releases

Packages

  0

Languages

Footer

Footer navigation