complete codex docs
This commit is contained in:
parent
b5dcf01a8c
commit
3cefad183d
62 changed files with 2730 additions and 50 deletions
26
docs/decisions/0005-control-path-layout.md
Normal file
26
docs/decisions/0005-control-path-layout.md
Normal file
|
|
@ -0,0 +1,26 @@
|
|||
# Decision 0005: Keep Managed Control Paths Outside Customer-Easy Edit Paths
|
||||
|
||||
## Status
|
||||
|
||||
Accepted
|
||||
|
||||
## Decision
|
||||
|
||||
Managed control files, manifests, scheduler state, and helper scripts should live in protected control locations rather than in customer-editable startup files where possible.
|
||||
|
||||
## Reasoning
|
||||
|
||||
- Customer-editable startup areas are too easy to tamper with.
|
||||
- Managed state should not depend on files that customers can modify through FTP or file manager.
|
||||
- Secure and auditable behavior is easier when control files are outside the customer content path.
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
- keep helper scripts in the game home
|
||||
- keep runtime manifests next to the game executable
|
||||
|
||||
## Why Those Were Not Chosen
|
||||
|
||||
- Those options make it too easy for customers to alter managed execution.
|
||||
- They complicate cleanup and lifecycle tracking.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue