Documents propose self-hosted OpenCode 2 for development and experiments
The documents propose evaluating self-hosted OpenCode 2 as an engineering assistant and experiment interface with separately approved models. The assessment reports no installation or runtime validation.
Proposed development interface
The proposal places OpenCode 2 in the development and research environment. The proposed architecture assigns production authorization, durable workflows and creator settlement to separate core services.
Proposed access conditions
The assessment distinguishes local software licensing from hosted service restrictions. It proposes requiring written permission for competing-model development through hosted OpenCode services. The proposed local route requires separate checks of model rights, permitted uses and training lineage.
Proposed tool boundaries
The assessment proposes starting with read-only information and reversible proposals through scoped tools. Attribution proposals cannot establish ownership or payable balances under this design. Experiment metrics remain separate from proposed payout decisions.
Files in this change
| File | Change | Lines |
|---|---|---|
README.md | modified | +1 −0 |
docs/OPENCODE_2_SOVEREIGN_SOURCE_RESEARCH.md | added | +227 −0 |
docs/PRODUCTION_SYSTEM_PLAN.md | modified | +2 −0 |