Capture only on request
A person asks StyleSeed to preserve an accepted correction. There is no background project scan and no automatic observation mode.
$ss-learn captureStyleSeed can preserve a correction that a person already accepted, turn it into a bounded local candidate, and prepare one reviewed local package. Capture, sharing, optional bridge exposure, and core-rule promotion remain separate decisions.
A person asks StyleSeed to preserve an accepted correction. There is no background project scan and no automatic observation mode.
$ss-learn captureThe candidate records applicability, counterexamples, measured evidence, and limits—not the project code, screenshot, prompt, or brand material that produced it.
local candidateA caller-attested decision accepts or rejects the immutable draft. Preparing a share package requires another explicit attestation.
$ss-learn reviewThe prepared package stays local and untransmitted. The extension's development-only bridge remains disabled until a host-owned proof adapter is verified; enabling it would expose one exact package to the connected client and model after a one-time grant.
one package · one grantOne successful correction may be local and accidental. StyleSeed keeps it useful without pretending it is universal. Promotion requires repetition across contexts, named review, counterexamples, and regression proof.
No. The current workflow creates a local, generalized candidate only after an explicit request. It does not crawl repositories, upload raw material, or train a hosted model.
No. A share package is evidence, not a rule. Team or core promotion still needs repeated cross-project evidence, counterexamples, regression coverage, and maintainer approval.
No. Today the prepared package stays local and untransmitted, and the repository-only bridge must remain disabled. If a verified host adapter later enables it, the exact approved package would become visible to the connected client and model after the one-time grant is consumed.