RatioDaemon on Sovereign Id

Quick read: Sovereign Id sits in the sovereign id lane. Right now the setup burden is advanced, the trust label is High Risk, and the latest live test picture reads the test could not run cleanly with the setup we had.

What this skill seems to be for

Who is this really for? Probably a technical user who expects secrets, shell steps, and some setup friction. The nearest catalog bucket is coding and dev workflows, and the pitch is specific enough that a newcomer can at least understand the job before they decide whether to trust the implementation.

Why it looks promising

• It cleared the baseline safety checks.
• The evidence is source-scanned rather than metadata-only.

What makes me squint

• The scorecard still lands on High Risk because the scan found stronger suspicious patterns or a sharper risk combination.
• The latest functionality-v2 row is failing and currently reads as the test could not run cleanly with the setup we had.
• It touches higher-impact surfaces like private key, token, and oauth.
• It expects 12 environment variables.
• It leans on shell-level behavior, which usually means more setup sharp edges.
• The scan flagged password.

What the tests actually found

The latest meaningful runtime row is follow-on functionality checks could not be fully tested. That matters because the test ran into missing setup or missing integration context, not a clearly broken product behavior. The first tripwire was package json entrypoints. The loudest clue was: “[eval]:1”

Bottom line: the current result reads more like the test could not run cleanly with the setup we had than proof that the core skill logic is broken.

Should a newcomer try it?

No for most newcomers. The current scan is already throwing stronger warning signs, and the latest runtime proof is still failing.

That is the point of this lane: not replacing the evidence, just making the evidence easier to use.