# Extending SCALE in an organization
Version 0.6 · Optional reference design

The portable kit works over supplied files and explicit saved state. It does not run a graph database, synchronize an EA platform, enforce enterprise permissions or operate a hosted service.

Consider integration only after bounded analyses show useful results and the review/maintenance work is sustainable. Choose a specific recurring question, a source owner, an accepted relationship model and a measurable service expectation before choosing infrastructure.

## Responsibilities
| Responsibility | Portable practice today | Possible integrated implementation |
|---|---|---|
| Source authority | Named sources, dated evidence, exact locators and recorded limitations | Permission-aware connectors to governed repositories |
| Architecture identity | Stable element IDs and typed atomic JSON relationships | EA repository or graph, with governed identity resolution |
| Retrieval | Supplied files, inspected citations and bounded questions | Search/index services that preserve source permissions |
| Human review | Recorded reviewer, disposition, date and rationale | Authenticated workflow and audit trail |
| Continuity | Validated saved JSON and generated views | Versioned storage with retention, access and recovery controls |
| Maintenance | Named steward, triggers and open-item register | Funded operating ownership and service expectations |

A JSON reviewer field is a record of supplied review information; it is not authenticated proof of approval. A schema can validate a field's shape but cannot establish enterprise truth. Access classification is a handling instruction, not an access-control mechanism.

## Minimum investment case
Name the questions to support, current effort and defects, sources/owners, review capacity, evidence obligations, and operating cost. Demonstrate that retrieval and maintenance will reduce more work than they create. Start with one bounded implementation and publish its limitations.

## Adoption gates
1. The basic case can be completed with an inspectable brief and valid saved state.
2. A correction survives a new session and the second question reuses the right knowledge.
3. Reviewers can find the underlying source and explain rejected interpretations.
4. A source change invalidates affected claims rather than silently preserving stale conclusions.
5. A named operating owner can maintain the model and meet review commitments.
6. The chosen platform's identity, permissions, retention and audit meet local requirements.

Retire or redesign integration if sources cannot remain current, reviewers have no capacity, the system cannot preserve permissions, or a simpler workflow answers the question at lower total cost.

The earlier expansive [SCALE reference architecture](https://stephenklahr.com/downloads/scale-reference-architecture.md) remains available as a historical design discussion. It is not a statement of functionality implemented by the portable kit.