Metadata-Version: 2.5
Name: cf-concept-installation
Version: 0.1.1
Summary: Cogniflow installation vocabulary and validation shapes.
Author: Cogniflow Maintainers
Requires-Python: >=3.11
Description-Content-Type: text/markdown

# cf-concept-installation

This package owns the vocabulary and SHACL shapes shared by installation
providers. It exposes three files through `cogniflow.semantic_sources`:

- `package.trig` describes the concept package.
- `concept.trig` groups the installation profile, profile catalog and plan
  vocabulary by concept domain.
- `shapes.trig` defines the corresponding validation rules.

The installation-profile and catalog IRIs are carried over from
`cf-concept-installation-profile`. Load the new vocabulary in place of the old
provider. Historical profile documents and their digests remain unchanged; they are not
migrated to the registered-profile format by this release.

## Registered-profile documentation (0.1.1)

A registered installation profile must have exactly one string value for each
of `skos:prefLabel`, `skos:definition`, `skos:scopeNote` and `skos:example`.
Its identifier, version and capability requests still use the existing typed
attributes and relations. The profile shape remains closed: unknown properties
and ontology-definition properties such as `rdfs:subClassOf` are not allowed.
Profiles are instances of the existing vocabulary, not places to define new
ontology terms.

In 0.1.0 the core documentation rule required a scope note and example on
Cogniflow-owned named resources, including `urn:cf:profile:minimal`, while the
closed installation-profile shape forbade those very properties. Adding the
documentation failed the profile check; omitting it failed the core check.
Version 0.1.1 fixes the profile shape, not the core rule or the profile namespace.
It permits and requires both properties with `minCount 1`, `maxCount 1` and
`xsd:string`, retaining all other constraints.

The standalone `tests/fixtures/documented-profile.trig` demonstrates this format.
The focused tests combine the installation shapes with the actual pinned
`cf_ontology/semantics/documentation.shapes.trig` from this source revision.
They check a complete profile, missing documentation, incorrect value types,
multiple values, forbidden properties and required installation attributes.
No replacement core documentation rule or runtime dependency is introduced.

This source correction does not rewrite the published 0.1.0 wheel, historical
`stonecastle/profiles` documents, their local adapter, installer version pins,
or frozen installer catalogs and evidence. Registration and publication require
later independent source and exact-artifact review; coordinated source/installer
full gates belong to the integration milestone.

A profile requests capabilities. A concrete `cf.bootstrap.plan.v2` describes
the lifecycle and source mode before artifact selection. A semantic plan
descriptor can identify its profile and bind the existing plan bytes by digest.
Artifact selection and installation authority remain governed by the existing
bootstrap contracts.

Bootstrap process declarations identify the console script, versioned JSON-RPC
protocol and request method. The provider's manifest links the declaration with
`hub:providesProcess`. The subprocess contract is distinct from the callable
Python service affordance used after bootstrap handoff.
