kumwe / interface-standard

v0.1.2 2026-09-08 16:08 UTC

Requires

• php: ^8.5
• ext-mbstring: *
• kumwe/access-control: 0.1.2
• kumwe/contribution: 0.1.1

Requires (Dev)

• phpstan/phpstan: ^2.1
• squizlabs/php_codesniffer: ^4.0

Apache-2.0

Published on Packagist.org on 2026-09-08 16:10 UTC

README

Portable interface values, strict owner-bound surface declarations and deterministic Kumwe Interface Standard 1.0 conformance diagnostics under Kumwe\InterfaceStandard.

Installation

composer require kumwe/interface-standard:0.1.2

Requires PHP ^8.5, ext-mbstring, Contribution 0.1.1 and Access Control 0.1.2, available from Packagist. Pre-1.0 consumers use an independently verified exact package version.

use Kumwe\Contribution\ContributionOwner;
use Kumwe\InterfaceStandard\SurfaceDefinition;

$surface = SurfaceDefinition::fromArray(
    ContributionOwner::extension('acme/orders'),
    $manifestSurface,
);
$canonicalMetadata = $surface->toArray();

Run composer examples for a complete declaration. Parsing enforces exact keys, bounded lists, supported versions, plain-text metadata and ownership. Semantic admission reports errors for actor/area, intent/pattern, required states, customization scope and responsive priorities.

Contract with Kumwe Core

The package owns vocabulary, typed declarations and semantic conformance. Capability references describe requirements; Core enforces them. Rendering, routes, navigation trees, trust, active-generation admission, authorization and presentation-preference state/persistence belong to Core and other consuming hosts.

There is no container provider or hidden global registry. Consumers construct the package values and stateless validator directly, using canonical Contribution ownership and Access Control capability types. See integration and architecture for the exact boundary.

API and development

Public API documents every signature and invariant. The release contract record preserves source mappings, manifest digests, compatibility requirements and consumer/test ownership. Historical source mappings do not assert current Core adoption.

composer install
composer check

The complete gate checks syntax, API and source closure, architecture, static analysis, style, behavior, examples, dependency security, archive consumers and release automation. composer clean-consumer installs the real distribution ZIP into a fresh production-only authoritative-classmap consumer. Verification explains evidence and explicit development dependency overrides.

Releases and license

The version badge follows Packagist; the CI badge follows the actual default-branch package workflow. Publication, passing package CI and independent artifact verification remain separate facts. Release policy requires stable source identity and preserves existing artifacts.

Licensed under Apache-2.0. See security policy.