跳转至

简体中文

Skill Family Foundation Workspace

The shared engineering-infrastructure parent workspace for the Skill Family lifecycle. This repository provides the machine contracts (Contracts), the thin Node runtime (Harness), the engineering kit (Engineering Kit), the Profile SPI, fully fictional generic sample fixtures, and the engineering documentation skeleton.

Current Status

This repository is a first-version skeleton under development. Dynamic state such as versions, releases, Pages, and Git is recorded solely in Current Product Status; the license is approved as Apache License 2.0, with the copyright holder being 广州市风荷科技有限公司 (Guangzhou Fenghe Technology Co., Ltd.). The full text is in the root-level LICENSE.

This workspace is permanently private and is the single source of truth for development; the only public boundary consists of three versioned release mirrors and the npm tarball. The pinned consumer coordinates and release status are recorded solely in Current Product Status.

The single product-level status page is Current Product Status, mechanically verified by node scripts/docs/fact-check.mjs against the machine source of truth; other pages do not carry a second status caliber.

First-Version Composition

Component Path Responsibility
Contracts packages/skill-family-contracts Sole authority for machine-executable engineering structure and mechanism protocols
Harness packages/skill-family-harness-node Implements only the mechanism protocols defined by Contracts; owns no business semantics
Engineering Kit packages/skill-family-engineering-kit Provides only the four top-level commands scaffold, adopt-plan, projection, check
Profile seed profiles/public-plugin Profile seed in the form of a public plugin
Fictional sample fixtures/generic-profile-extension-conformance A fully fictional extension-conformance sample

The package manifest, Profiles, fixtures, and top-level commands use .foundation/skeleton-manifest.json as the machine source of truth; tool version locks are in .foundation/version-lock.json.

Documentation Map

Writing Boundaries

Documentation consumes only a frozen fact package composed of the machine source of truth (manifest, package.json, Contracts registry, etc.), mechanically verified by node scripts/docs/fact-check.mjs. Model names, credentials, and scheduling information do not enter documentation, nor do they enter Contracts; see Architecture Boundaries.