# HyperTwist Phase S1-A first-party skill registry and manifest contract preparation packet

Created on `2026-05-28`

## Status

- first-party HyperTwist packet
- source-backed `Phase S1-A` preparation/control slice

## Purpose

This packet scopes the first bounded product implementation slice under the
canonical `Skillization And Command Surface` doctrine.

The granted slice is:

- first-party skill manifest schema
- skill id, version, owner lane, and status fields
- command/service binding declaration
- permission/scope declaration
- provenance/log declaration

It is not:

- menu/settings/off-state controls
- invocation/provenance audit ledger execution
- permissive analyzer wrappers
- restrictive clean-room command-contract specs

## Current authority basis

This control pass stands on:

- `docs/ops/HYPERTWIST_SKILLIZATION_AND_COMMAND_SURFACE_DOCTRINE_2026-05-21.md`
- `docs/ops/HYPERTWIST_OPTIONAL_ASSISTIVE_FEATURE_DEACTIVATION_AND_REMOVABILITY_DOCTRINE_2026-05-21.md`
- `docs/ops/HYPERTWIST_IMPLEMENTATION_PHASE_1_KICKOFF.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/ARCHITECTURE.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/FEATURE_REGISTRY.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/SKILLS.md`
- `docs/v6_5_deep_manual_pack/HyperTwist/PROVENANCE_AND_TRUST_MODEL.md`

The preserved owners do not change here:

- first-party HyperTwist remains the owner of the product command surface
- optional assistive skills remain product-owned adjuncts rather than donor
  command truth
- analyzer, memory, provider, and domain skill families remain bounded future
  families rather than shipped wrappers

## Granted family

The bounded `Phase S1-A` slice may land:

1. first-party skill status and family enums
2. command/service binding declarations
3. permission/scope declarations
4. provenance/log declarations
5. per-skill manifest entries and registry counts
6. sample registry contract and JSON round-trip coverage

The packet must stay out of:

- real enable/disable settings behavior
- menu visibility controls
- actual invocation ledger storage
- broad wrapper implementation

## Proposed implementation shape

Land the narrower first-party boundary through:

- new skill types for:
  - skill status
  - skill family
  - command bindings
  - permission scopes
  - provenance declarations
  - manifest entries
  - registry state
- a first-party skill-core library that derives a bounded registry state
- sample-contract helpers for:
  - sample registry derivation
  - JSON serialization
  - JSON deserialization
- focused automation in:
  - `HyperTwistSkillPhaseS1ARegistryManifestContractTest.cpp`

## Validation target

Validate with:

- Unreal build for `UnrealHyperTwistEditor Win64 Development`
- focused automation:
  - `HyperTwist.FirstParty.Skill.PhaseS1A.RegistryManifest`
  - `HyperTwist.FirstParty.Skill.PhaseS1A.DisabledSkillsRemainInstalled`
  - `HyperTwist.FirstParty.Skill.PhaseS1A.SerializationRoundTrip`

## Queue effect

If this packet lands cleanly:

- `S1-A` is consumed
- `S1-B` becomes the next clean move
- do not jump straight from `S1-A` to analyzer wrappers or restrictive specs
