Related canonical identities, organized together. A shared family is not a claim that every release is mutually compatible or equally qualified.
Composite KOURAN security model combines authority/bounds/rights, epoch revocation, domain isolation, object versioning, replay checks and an external hardened cryptographic boundary.
Source / reference evidenceExecution is driven by continuation tokens rather than SKYRA hyperblocks; a continuation becomes eligible when dependency tokens, authority state and expected object version satisfy the architectural contract.
Source / reference evidenceOne morphable PE lattice is intended to map dense matrix, sparse tensor, vector, reduction, graph and solver/search primitives rather than separate fixed-function dense/sparse islands.
Source / reference evidenceStable SRAM and streaming PHY wrappers isolate KOURAN digital logic from foundry/vendor memory and I/O hard macros so the architecture can target SKY130, N2, 18A-class and package-specific implementations.
Source / reference evidenceFine-grained side-effect segments journal destination/value updates and discard them on fault or drain them only after commit, avoiding whole-hyperblock recovery granularity.
Source / reference evidenceStart with a chip, a software release or a single IP block.