gonol-build

Files (1)

• SKILL.md

SKILL.md (first lines)

# gonol-build

## Workflow

1. Resolve the exact UCNS authority and the exact owning Stack research workspace before building.
2. Before launching construction or replay whose completion materially depends on scarce resources, preflight the resources required to finish the declared scope.
3. Resolve the owning Stack workspace's declared source/admission profile, participant eligibility, relations, and closure rules; do not impose a universal adjacent-scale ladder.
4. Consume UCNS gonol constructors and geometry rather than defining a competing gonol object in the language layer.
5. Close each completed gonol before it participates atomically at an admissible consuming scale.
6. If required UCNS geometry is unresolved, preserve that boundary as `hmmm`.
7. Replay the complete declared scope only where replay is required by the governing protocol.

## Authority

```text
UCNS      = gonol objects, constructors, and underlying geometry
Stack     = active language-gonol construction research workspaces
EDCM      = measurement and evaluation of constructed outputs
skill-lib = construction/replay discipline
```

Repository placement does not transfer authority. A Stack workspace may construct English, Python, French, TypeScript, or another domain from UCNS gonol objects without thereby owning UCNS geometry. Language workspaces consume UCNS construction authority; they do not redefine it. EDCM may measure a completed construction without defining that construction.

Historical EDCM constructor names and sealed artifacts remain valid historical identities for replay. They do not restore active construction authority to EDCM.

## Active construction contract

```text
declared source/admission profile
+ eligible already-closed participants
+ constitutive relation
+ UCNS gonol construction
-> closure
```

The active constructor contract belongs to the owning Stack research workspace. Resolve its exact files and commit before selecting participants. For the current English research workspace this includes `research/english-gonol/`; for current Python research this includes `research/python-gonol/`. These paths are workspace locations, not universal language canon.

The sequence `characters -> words -> definitions -> recursive relations` may describe a particular construction, but it is not a mandatory ladder for every language or every admitted construction.

- Every admitted primitive occurrence required by the active profile remains individually addressable.
- Ordered closed gonols may close into a higher construction when the owning workspace authorizes that relation.
- Any closed gonol is atomic at an admissible consuming scale while constituent identities, order, multiplicity, source positions, relations, and provenance remain recoverable.
- Constitutive relationships belong inside the construction. Sidecars may index or cache them but must not replace them.
- Recursive relations consume already-closed gonols without reopening or erasing their internal structure.

Do not invent participant eligibility, a required intermediate stage, semantic axes, or a geometry law merely to complete a pipeline.

## Pronunciation boundary

Pronunciation is not required by default. Pronunciation, phonetic spelling, IPA, audio, or other sound representations must not alter gonol identity, closure, ordering, or relations unless the owning construction explicitly admits phonology.

Source pronunciation data may remain evidence or metadata. It becomes construction only under an explicit source/admission contract.

## Construction invariant

At every admitted scale:

```text
ordered eligible closed gonols
-> constitutive relation declared by the owning workspace
-> UCNS gonol construction / authorized geometric application
-> closure
-> deterministic identity + provenance receipt
-> atomic participation at an admissible consuming scale
```

Preserve exact source identity, occurrence order, multiplicity, relation identity, and provenance. Do not normalize, deduplicate, infer relations, or substitute tokens, AST nodes, compiler objects, embeddings, hashes, or metadata for gonol construction unless the active contract explicitly authorizes their role.

If required UCNS geometry is unresolved, preserve that boundary as `hmmm`; do not fill it with an invented rule.

## Candidate boundary

An unresolved constructor or geometry operation permits named, bounded candidate work where the declared evidence permits it. It does not block declared experimentation. It blocks promotion beyond the evidence.

## Completion and replay

Before launching a construction or replay run whose completion materially depends on scarce resources, preflight the resources required to finish it. If the preflight cannot establish enough resource confidence to finish the declared scope, do not start the compute run; record the resource boundary as `hmmm` or narrow the declared scope under the governing protocol. Once a healthy admitted run begins, let it reach its natural terminal condition unless a genuine safety/resource boundary or preregistered load-bearing stop condition fires. Do not add arbitrary wall-clock limits.

A completion claim requires:

1. exact UCNS, Stack workspace, source/profile, and constructor identities;
2. the complete declared source scope;
3. deterministic construction receipts; and
4. independent complete replay where replay is required by the governing protocol.

Replay establishes reproducibility of that construction only. It does not by itself establish semantic quality, measurement validity, cognition claims, or canon outside the declared scope.

## Usage guidance

For active gonol-language construction, start in the owning research workspace inside `The-Interdependency/stack` and consume current UCNS gonol constructors/geometry. Do not start in EDCM.

```text
UCNS:  gonol objects + constructors + geometry
Stack: active construction research
EDCM:  measurement/evaluation only
```

Use `stack-update` when ownership, placement, authority, lifecycle, or promotion changes. Use `interdependent-work-graph` whenever the task crosses repository boundaries.

Run skill-lib's local authority regression gate after changing this boundary:

```bash
bash tools/check_gonol_authority.sh
```

## Anti-patterns

- Assigning active gonol or language construction authority to EDCM.
- Defining a competing gonol object in an English, Python, or other language workspace instead of consuming UCNS construction authority.
- Treating Stack placement as transfer of UCNS geometry authority.
- Imposing an adjacent-scale ladder or inventing an eligible relation without the owning workspace's authority.
- Letting pronunciation alter gonol identity, closure, ordering, or relations unless an explicit construction admits it.
- Normalizing, deduplicating, inferring relations, or substituting tokens, AST nodes, embeddings, hashes, or metadata for gonol identity unless explicitly authorized.
- Adding arbitrary wall-clock limits to a healthy admitted run.
- Treating replay as semantic quality, measurement validity, cognition, or extra-scope canon.

## hmmm

- exact UCNS geometric operations that remain unresolved in current implementation;

From The-Interdependency/skill-lib, MPL-2.0.

More from The-Interdependency/skill-lib