Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
External research report
Data sources: ZENODO
addClaim

A6 Composition Layer v0.1.1: Hybrid / Federated Anchor Composition Profile for c = a + b

Authors: Kotov, Ivan;

A6 Composition Layer v0.1.1: Hybrid / Federated Anchor Composition Profile for c = a + b

Abstract

This release publishes A6 Composition Layer v0.1.1, a boundary profile for hybrid and federated anchor composition in the c = a + b framework. The profile formalizes A6 as an anchor-composition state over A0–A5, not as a merged super-anchor. It defines mandatory maps for participating anchors, standing, authority, memory compartments, sensors, jurisdiction, Experience Artifacts, revocation, exit, split handling, and resource/custodian responsibility. The release distinguishes A6-EXIT from A6-SPLIT: A6-EXIT = revoke-and-continue.A6-SPLIT = freeze-and-escalate. The package also includes Anchor Class Boundaries v0.2.1, which provides the protocol-facing taxonomy for anchor classes in c = a + b and points to the A6 Composition Layer for detailed A6 behavior. This work is a protocol and research artifact. It does not create legal personhood, public authority, product certification, public-law activation, or post-anchor sovereignty. Applicable law remains external to the protocol.

Powered by OpenAIRE graph
Found an issue? Give us feedback