@kanonak-protocol/sdk 4.12.0 → 4.14.0

package/dist/validation/ValidationCache.d.ts

@@ -1,94 +1,52 @@
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { Kanonak } from '../kanonaks/Kanonak.js';
 /**
- * Per-validation-pass memoization shared across every repository rule
- * applied to documents in the same repository.
+ * Per-validation-pass memoization shared across every repository rule applied to
+ * documents in the same repository.
  *
- * Today the validator's caller (CLI single-file validation, or the
- * VS Code diagnostics provider validating every workspace document)
- * runs `KanonakObjectValidator.validateAsync(doc, repo)` once per
- * document. Each call re-executes 21 repository rules from scratch
- * against the same repository, and several of those rules redo
- * identical work for every document — walking the import closure
- * to collect class declarations, looking up the same package via
- * `getHighestCompatibleVersionAsync` over and over, or re-parsing
- * the entire repo through `KanonakObjectParser`.
+ * The expensive shared work is the full-repository `parseKanonaks`. Every
+ * repository rule reads the resolved object model (the merged catalog via
+ * {@link getKanonaks}, or the pre-merge per-document authored view via
+ * {@link getAuthoredKanonaks}); the cache parses the repo at most ONCE per pass
+ * and serves both views from that single parse. A batch caller
+ * (`KanonakObjectValidator.validateDocumentsAsync`) constructs one cache and
+ * threads it through every per-document `validateAsync`, so validating a whole
+ * directory is one parse, not O(documents x catalog).
  *
- * `ValidationCache` is the seam that lets a multi-document caller
- * share that work across calls. The cache's lifetime is one
- * validation pass over one repository; the diagnostics provider
- * constructs a fresh cache at the top of each refresh and passes
- * it to every per-document `validateAsync`. Rules opt in by
- * reading from the cache when present; without it they fall back
- * to their original logic (used by single-document callers like
- * the CLI's `kanonak validate <path>`).
- *
- * The cache also exposes a wrapped `repository` that memoizes
- * `getHighestCompatibleVersionAsync` and
- * `getDocumentsByNamespaceAsync` — both linear scans over the
- * in-memory repo. Rules that don't know about the cache still
- * benefit, because the validator passes `cache.repository` as the
- * repo argument so their existing lookup calls hit the cache
- * transparently.
+ * The cache also exposes a wrapped {@link repository} that memoizes the two
+ * linear-scan repository lookups (`getHighestCompatibleVersionAsync`,
+ * `getDocumentsByNamespaceAsync`); rules that call the repository directly hit
+ * the cache transparently because the validator passes `cache.repository` as the
+ * repo argument.
  */
 export declare class ValidationCache {
     private readonly underlying;
     /**
-     * Repository wrapper that memoizes read-only lookups for the
-     * lifetime of this cache. Pass this to every rule (instead of
-     * the bare repository) so existing rule code that calls
-     * `repository.getHighestCompatibleVersionAsync(...)` benefits
-     * automatically without needing to know about the cache.
+     * Repository wrapper that memoizes read-only lookups for the lifetime of this
+     * cache. Pass this to every rule (instead of the bare repository) so existing
+     * rule code that calls `repository.getHighestCompatibleVersionAsync(...)`
+     * benefits automatically without needing to know about the cache.
      */
     readonly repository: IKanonakDocumentRepository;
-    private kanonaksPromise;
-    private importClosureCache;
-    private classDeclarationsCache;
-    private propertyNamesCache;
-    private allDocumentsPromise;
+    private parsePromise;
     constructor(underlying: IKanonakDocumentRepository);
     /**
-     * Full-repository `parseKanonaks` result, memoized for the cache's
-     * lifetime. Used by rules that want the resolved-URI object model
-     * (e.g. `MarkdownLinkRule`) instead of walking raw `document.body`.
-     * Filter by `subject.namespace` to scope to a specific document.
+     * Full-repository `parseKanonaks` result (the open-world-merged catalog),
+     * memoized for the cache's lifetime. Filter by `subject.namespace` to scope to
+     * a specific document.
      */
     getKanonaks(): Promise<Kanonak[]>;
     /**
-     * Identifier-keyed transitive-import closure for the given document.
-     * Returns the set of `publisher/package@version` strings reachable
-     * via `imports:` starting from `docId`, including `docId` itself.
-     *
-     * Rules that need to know "what does this document import,
-     * recursively?" should call this once instead of walking the
-     * imports graph themselves on every reference lookup. Per-doc
-     * memoized; same doc validated multiple times in the pass
-     * traverses the graph once.
-     */
-    getImportClosure(docId: string): Promise<Set<string>>;
-    /**
-     * subClassOf relationships declared inside the given document's
-     * body (NOT in its imports). Map<className, parentClassName[]>.
-     * Composed across an import closure to build the effective class
-     * hierarchy a rule needs.
-     *
-     * Cached per-doc so two rules consulting the same document's
-     * declarations (or the same document validated multiple times)
-     * walk its body once.
-     */
-    getClassDeclarations(docId: string): Promise<Map<string, string[]>>;
-    /**
-     * Names of property-typed entities (`ObjectProperty`,
-     * `DatatypeProperty`, `AnnotationProperty`, plain `Property`)
-     * declared inside the given document's body. Used by reference-
-     * resolution rules to answer "is property P defined here?" in O(1)
-     * after a one-time scan.
+     * The PRE-MERGE, per-document parse from the SAME single full-repo parse as
+     * {@link getKanonaks}: each document's authored subjects (and embeddeds),
+     * stamped with their `sourceDoc`, before the open-world merge folds them onto
+     * shared URIs and dedups cross-document duplicates. A per-document rule that
+     * must validate exactly what a document authored — including augmentations it
+     * asserts about imported entities, which the merge files under the imported
+     * namespace — filters this by `sourceDoc`, instead of re-parsing the document
+     * (which would break the ≤1-parse contract). Resolution targets still come
+     * from the merged {@link getKanonaks}.
      */
-    getPropertyNames(docId: string): Promise<Set<string>>;
-    private getAllDocuments;
-    private computeImportClosure;
-    private buildDocsByIdIndex;
-    private computeClassDeclarations;
-    private computePropertyNames;
-    private findDocById;
+    getAuthoredKanonaks(): Promise<Kanonak[]>;
+    private parseOnce;
 }

package/dist/validation/documentModel.d.ts

@@ -1,5 +1,5 @@
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
-import type { KanonakDocument } from '@kanonak-protocol/types/document/models/types';
+import type { KanonakDocument, Import, DocumentReference } from '@kanonak-protocol/types/document/models/types';
 import type { ValidationCache } from './ValidationCache.js';
 import type { Kanonak } from '../kanonaks/Kanonak.js';
 import { DefinedKanonak } from '../kanonaks/DefinedKanonak.js';
@@ -29,6 +29,24 @@ export declare function getCatalogKanonaks(document: KanonakDocument, repository
  * captured data.)
  */
 export declare function getDocumentKanonaks(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<Kanonak[]>;
+/**
+ * The subjects THIS document authored — INCLUDING the open-world augmentations
+ * it asserts about imported entities. An augmentation (e.g. a look package
+ * adding `semanticSvg` to `rdfs.Resource`) is filed under the IMPORTED package's
+ * namespace by the open-world merge, so {@link getDocumentKanonaks} — which
+ * scopes by the document's own namespace — does not return it. This reads the
+ * parser's PRE-MERGE view (each subject + embedded stamped with its authoring
+ * `sourceDoc`) from the SAME single parse as {@link getCatalogKanonaks}, then
+ * keeps the subjects this document authored. Unlike a re-parse it preserves the
+ * ≤1-parse batch contract; unlike the merged catalog it does not lose a
+ * document's authored statements to cross-document de-duplication.
+ *
+ * Use this when a rule must validate what a document authored regardless of
+ * which namespace the merge files it under (e.g. an embedded `type:` on an
+ * augmentation). Resolution targets are still looked up against
+ * {@link getCatalogKanonaks}.
+ */
+export declare function getAuthoredKanonaks(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<Kanonak[]>;
 /** A DefinedKanonak visited during a walk, with a human-facing locator path. */
 export interface WalkNode {
     readonly kanonak: DefinedKanonak;
@@ -46,3 +64,31 @@ export declare function walkDefinedKanonaks(roots: Kanonak[], visit: (node: Walk
 /** `publisher/package@major.minor.patch` — matches `SubjectKanonak.namespace`
  * and the parser's `sourceDoc`. Undefined for a document without a namespace. */
 export declare function namespaceOf(document: KanonakDocument): string | undefined;
+/**
+ * Cacheless catalog source: exposes the target document PLUS every other
+ * document in the backing repository through `getAllDocumentsAsync` (and
+ * delegates all resolution lookups to the backing repository). This lets the
+ * single-document parse see the whole import closure — so cross-package
+ * references resolve to real imported subjects, matching the cached (batch)
+ * path. The target document is listed first and any same-namespace copy in the
+ * repository is excluded, so the in-hand document stays authoritative for its
+ * own namespace even when an older copy was saved. Unlike
+ * `SingleDocumentRepository` (which exposes ONLY the target document, by
+ * design, for parsing one entity in isolation), this includes the closure
+ * precisely because validation existence checks need it.
+ */
+export declare class DocumentWithRepositoryCatalog implements IKanonakDocumentRepository {
+    private readonly document;
+    private readonly broader;
+    constructor(document: KanonakDocument, broader: IKanonakDocumentRepository);
+    getAllDocumentsAsync(): Promise<KanonakDocument[]>;
+    getDocumentAsync(identifier: string): Promise<KanonakDocument | null>;
+    getDocumentsByNamespaceAsync(publisher: string, package_: string): Promise<KanonakDocument[]>;
+    getHighestCompatibleVersionAsync(publisher: string, import_: Import): Promise<KanonakDocument | null>;
+    getAllDocumentReferencesAsync(): Promise<DocumentReference[]>;
+    getDocumentContentAsync(identifier: string): Promise<string | null>;
+    getDocumentUriAsync(identifier: string): Promise<string | null>;
+    saveDocumentAsync(): Promise<void>;
+    deleteDocumentAsync(): Promise<void>;
+    clearNamespaceAsync(): Promise<void>;
+}

package/dist/validation/index.d.ts

@@ -8,4 +8,4 @@ export { KanonakObjectValidator } from './KanonakObjectValidator.js';
 export type { IDocumentValidationRule } from './rules/document/IDocumentValidationRule.js';
 export type { IRepositoryValidationRule } from './rules/repository/IRepositoryValidationRule.js';
 export { NamespacePrefixRule, ResourceNamingRule, PropertyTypeSpecificityRule, SubjectKanonakTypeRequiredRule, PackageHeaderRule } from './rules/document/index.js';
-export { ImportExistenceRule, UnresolvedReferenceRule, ClassHierarchyCycleRule, PropertyHierarchyCycleRule, PropertyRangeRequiredRule, SubClassOfReferenceRule, SubPropertyOfReferenceRule, NamespaceImportCycleRule, UnresolvedPredicateRule, DefinitionPropertyReferenceRule, XsdImportRule, AmbiguousReferenceRule, PropertyRangeReferenceRule, ObjectPropertyImportRule, ObjectPropertyValueValidationRule, PropertyDomainRule, PropertyValueTypeRule, ClassDefinitionRule, EmbeddedKanonakTypeRule, MarkdownLinkRule, DisplayLensScopeRule, LookSemanticSvgPathRule, TxExpressionPathRule, ShaclShapeRule, OwlOneOfRule, DiamondNameClashRule } from './rules/repository/index.js';
+export { ImportExistenceRule, UnresolvedReferenceRule, ClassHierarchyCycleRule, PropertyHierarchyCycleRule, PropertyRangeRequiredRule, SubClassOfReferenceRule, SubPropertyOfReferenceRule, NamespaceImportCycleRule, UnresolvedPredicateRule, AmbiguousReferenceRule, PropertyRangeReferenceRule, ObjectPropertyValueValidationRule, PropertyDomainRule, PropertyKindRangeConsistencyRule, ClassDefinitionRule, EmbeddedKanonakTypeRule, MarkdownLinkRule, DisplayLensScopeRule, LookSemanticSvgPathRule, TxExpressionPathRule, ShaclShapeRule, OwlOneOfRule, DiamondNameClashRule } from './rules/repository/index.js';

package/dist/validation/index.js

@@ -1 +1 @@
-import{A,B,C,D,E,F,G,H,I,L as J,M as K,a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z}from"../chunk-UBBZWWRB.js";import"../chunk-SHDHMKMJ.js";import"../chunk-BKVPSPG4.js";import"../chunk-NJ3AZYQD.js";import"../chunk-IEOSSSB5.js";import"../chunk-7TKJHKC2.js";import"../chunk-7HRKWTBB.js";import"../chunk-4UT2CLAT.js";import"../chunk-FUUTGGJS.js";import"../chunk-2ACBWC7K.js";export{w as AmbiguousReferenceRule,C as ClassDefinitionRule,n as ClassHierarchyCycleRule,u as DefinitionPropertyReferenceRule,J as DiamondNameClashRule,E as DisplayLensScopeRule,k as EmbeddedKanonakTypeRule,l as ImportExistenceRule,K as KanonakObjectValidator,F as LookSemanticSvgPathRule,D as MarkdownLinkRule,s as NamespaceImportCycleRule,f as NamespacePrefixRule,y as ObjectPropertyImportRule,z as ObjectPropertyValueValidationRule,c as OntologyValidationError,a as OntologyValidationResult,I as OwlOneOfRule,j as PackageHeaderRule,A as PropertyDomainRule,o as PropertyHierarchyCycleRule,x as PropertyRangeReferenceRule,p as PropertyRangeRequiredRule,h as PropertyTypeSpecificityRule,B as PropertyValueTypeRule,g as ResourceNamingRule,H as ShaclShapeRule,q as SubClassOfReferenceRule,r as SubPropertyOfReferenceRule,i as SubjectKanonakTypeRequiredRule,G as TxExpressionPathRule,t as UnresolvedPredicateRule,m as UnresolvedReferenceRule,e as ValidationCache,d as ValidationContext,b as ValidationSeverity,v as XsdImportRule};
+import{A,B,C,D,E,F,I as G,J as H,a,b,c,d,e,f,g,h,i,j,k,l,m,n,o,p,q,r,s,t,u,v,w,x,y,z}from"../chunk-MRNELSJF.js";import"../chunk-R73T4RUO.js";import"../chunk-NJ3AZYQD.js";import"../chunk-2HNPPYSK.js";import"../chunk-6U26UASC.js";import"../chunk-WGKIRLMA.js";import"../chunk-7BHDZHJY.js";import"../chunk-FUUTGGJS.js";import"../chunk-2ACBWC7K.js";export{u as AmbiguousReferenceRule,z as ClassDefinitionRule,n as ClassHierarchyCycleRule,G as DiamondNameClashRule,B as DisplayLensScopeRule,k as EmbeddedKanonakTypeRule,l as ImportExistenceRule,H as KanonakObjectValidator,C as LookSemanticSvgPathRule,A as MarkdownLinkRule,s as NamespaceImportCycleRule,f as NamespacePrefixRule,w as ObjectPropertyValueValidationRule,c as OntologyValidationError,a as OntologyValidationResult,F as OwlOneOfRule,j as PackageHeaderRule,x as PropertyDomainRule,o as PropertyHierarchyCycleRule,y as PropertyKindRangeConsistencyRule,v as PropertyRangeReferenceRule,p as PropertyRangeRequiredRule,h as PropertyTypeSpecificityRule,g as ResourceNamingRule,E as ShaclShapeRule,q as SubClassOfReferenceRule,r as SubPropertyOfReferenceRule,i as SubjectKanonakTypeRequiredRule,D as TxExpressionPathRule,t as UnresolvedPredicateRule,m as UnresolvedReferenceRule,e as ValidationCache,d as ValidationContext,b as ValidationSeverity};

package/dist/validation/rules/repository/ClassDefinitionRule.d.ts

@@ -2,11 +2,26 @@ import type { KanonakDocument } from '@kanonak-protocol/types/document/models/ty
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Every `type` target — the class an entity is declared an instance of — must
+ * resolve to a class-like resource. A built-in meta-class (`Class`,
+ * `ObjectProperty`, `Datatype`, `Package`, …) is itself a `type: Class` subject
+ * in the core packages, so it resolves the same way as a user-defined class —
+ * no hardcoded built-in allow-list is needed, and a real typo (`type: Conatiner`)
+ * is correctly flagged regardless of how it was aliased.
+ *
+ * Reads the resolved object model recursively ({@link walkDefinedKanonaks}), so
+ * a bad `type` on an embedded kanonak at any depth is caught, not just on
+ * top-level subjects (the #65 gap). The `type` target parses to a
+ * `ReferenceKanonak` whose `subject` URI the parser canonicalizes; existence +
+ * class-ness are checked by `findSubjectByUri` + `ResourceTypeClassifier`, never
+ * by a built-in-name set or `split('.')` alias extraction. (`type` is the
+ * structural predicate this rule owns — `UnresolvedReferenceRule` skips it.)
+ */
 export declare class ClassDefinitionRule implements IRepositoryValidationRule {
-    private readonly builtInClasses;
-    get ruleName(): string;
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    private checkNestedTypes;
-    private isClassEntity;
-    private isDefinitionType;
+    readonly ruleName = "ClassDefinition";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
+    private resolvesToClassLike;
+    private error;
 }

package/dist/validation/rules/repository/ClassHierarchyCycleRule.d.ts

@@ -2,10 +2,15 @@ import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/documen
 import type { KanonakDocument } from '@kanonak-protocol/types/document/models/types';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Detects a circular `subClassOf` hierarchy. Reads the resolved object model: the
+ * subClassOf graph is walked by canonical `KanonakUri` (resolved through the
+ * import closure) and compared by `uriKey` identity, so a cycle that closes
+ * across packages — where the same class is spelled with different aliases in
+ * each hop — is caught, where the old local-name hierarchy map would miss it.
+ */
 export declare class ClassHierarchyCycleRule implements IRepositoryValidationRule {
     readonly ruleName = "ClassHierarchyCycle";
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    private buildClassHierarchy;
-    private detectCycle;
-    private detectCycleRecursive;
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
 }

package/dist/validation/rules/repository/EmbeddedKanonakTypeRule.d.ts

@@ -2,101 +2,40 @@ import type { KanonakDocument } from '@kanonak-protocol/types/document/models/ty
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
 /**
- * Validates `type:` declarations on embedded kanonaks.
+ * Validates an explicit `type:` on an embedded kanonak against the range of the
+ * parent property it is embedded under: the declared type must be the range
+ * itself (redundant — a Warning) or a `subClassOf` descendant of it (accepted),
+ * supporting discriminated-union modelling with real OWL semantics.
  *
- * An embedded object MAY declare a `type:` property. If declared, the
- * declared type must be a subclass of (or equal to) the range of the
- * parent property under which the object is embedded. This relaxes
- * the previous "no explicit type on embeddeds" rule so authors can
- * model tagged-union / discriminated-union hierarchies with proper
- * OWL `subClassOf` semantics instead of working around the validator
- * with a separate discriminator class and named-instance enumeration.
+ * Reads the resolved object model, NOT raw `document.body`. The parser has
+ * already resolved every embedding predicate to its canonical property URI, so
+ * the parent property is known directly from the `EmbeddedStatement`/`ListStatement`
+ * predicate — collapsing the old local-name property-range map and its
+ * alias/parent-class disambiguation entirely. The subclass test is the single
+ * canonical `superClassChain` walk compared by `uriKey` identity, so a
+ * cross-package subclass resolves regardless of the alias spelling each document
+ * used (`fml.Expression` vs `Expression` both being `…/formula/Expression`) —
+ * fixing the string-comparison false-negative the old `isSubclassOfAsync` +
+ * local-name fallback produced (#65, comment 4). Coverage is recursive on
+ * embeddeds at any depth.
  *
- *   - Equal-to-range declarations are accepted but emit a Warning
- *     ("redundant"). Authors who want explicit redundancy can opt in
- *     by ignoring the warning.
- *   - Strict-subclass declarations are accepted (no diagnostic).
- *   - Non-subclass declarations error with a suggestion to either
- *     drop the type or add a matching `subClassOf:` to the declared
- *     class.
- *   - When the parent property has no `range:`, or the range is a
- *     "universal" class (`Resource`, `Class`), no constraint is
- *     enforced — every declared embedded type is accepted.
- *
- * Why this is a repository rule rather than a document rule: deciding
- * whether `cp.OrCondition` is a subclass of `Condition` requires
- * walking `subClassOf` across the importing document's transitive
- * imports, which the document-only validator interface can't reach.
- * The class hierarchy walk is delegated to
- * `ResourceResolver.isSubclassOfAsync`, the same helper other
- * range-aware rules already share.
+ *   - A "universal" range (`rdfs.Resource`, `rdfs.Class`) imposes no constraint.
+ *   - An embedded with no explicit `type:` is fine (the type is inferred).
+ *   - An unresolved parent property or range is reported by the dedicated
+ *     reference rules, not here.
  */
 export declare class EmbeddedKanonakTypeRule implements IRepositoryValidationRule {
-    get ruleName(): string;
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    /**
-     * Pick the right property-range candidate when multiple packages
-     * declare a property with the same local name (e.g. `tx.Not.operand`
-     * range `Expression` vs. `wv.NotCondition.operand` range `Condition`).
-     *
-     * Disambiguation strategy, in priority order:
-     *
-     *   1. If the property name as authored is alias-prefixed
-     *      (`tx.operand`), match candidates whose declaring entity
-     *      shares the same alias prefix. This is the unambiguous case
-     *      most authors hit — the YAML key carries the disambiguator.
-     *   2. Otherwise, if the parent dict has a `type:` declaration,
-     *      match candidates whose `domain` local-name equals the parent
-     *      class's local-name. The embedded under `type: tx.Not` only
-     *      reasonably refers to the `operand` property whose domain is
-     *      `tx.Not` (kanonak-protocol/typescript#17).
-     *   3. Last resort: return the first candidate. Authors who hit this
-     *      branch have a genuinely ambiguous shape — bare property name,
-     *      no parent type, multiple matching properties — and the rule
-     *      can't tell which they meant.
-     */
-    private pickRange;
-    /**
-     * Recursively descend through a YAML dict, validating any `type:`
-     * declarations encountered at depth > 0 against the closest known
-     * parent-property range.
-     *
-     * `parentPropertyRange` flows down from the property under which
-     * this dict sits. Two cases preserve it correctly:
-     *
-     * 1. **Single embedded under a property** — keys here are the
-     *    embedded's properties; we look up each key's own range and
-     *    pass it down for the next level.
-     * 2. **Dict-keyed list of embeddeds** (e.g.
-     *    `hasArgument: { foo: {...}, bar: {...} }`) — keys are labels
-     *    rather than properties, so they resolve to no range. In that
-     *    case we propagate the OUTER property's range through the
-     *    label level so the embedded values still get checked.
-     *
-     * List items are handled identically: a list under property P
-     * means each item is an embedded under P, regardless of whether
-     * the list is positional (`- item`) or dict-keyed.
-     */
-    private checkEmbeddedTypes;
-    private validateEmbeddedType;
-    private localName;
+    readonly ruleName = "EmbeddedKanonakType";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
     /**
-     * Build a map from property local name → list of candidate
-     * declarations (range + domain + declaring alias). Multiple
-     * candidates exist when more than one imported package declares a
-     * property with the same local name (e.g. `tx.Not.operand` range
-     * `Expression` AND `wv.NotCondition.operand` range `Condition`).
-     *
-     * Pre-#17, this map collapsed candidates by overwriting each prior
-     * entry, so the last-loaded property won and silently shadowed the
-     * others. Now all candidates are kept; `pickRange` picks the right
-     * one at lookup time using alias-prefix and parent-class context.
-     *
-     * The local-name keying mirrors the lookup pattern in
-     * `checkEmbeddedTypes` (which uses `localName(propertyName)` for
-     * the lookup). Same convention as `PropertyValueTypeRule` and
-     * `ObjectPropertyValueValidationRule`.
+     * Descend a node's statements: every embedded object (single or list item) is
+     * checked against its embedding property's range, then recursed into so a
+     * deeper embedded is checked against ITS own embedding property.
      */
-    private buildPropertyRangeMap;
+    private walk;
+    private check;
+    private redundant;
+    private notSubclass;
 }

package/dist/validation/rules/repository/ObjectPropertyValueValidationRule.d.ts

@@ -2,11 +2,25 @@ import type { KanonakDocument } from '@kanonak-protocol/types/document/models/ty
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * When an ObjectProperty's range is a schema-level meta-class, a value that
+ * REFERENCES an entity must reference one of that nature — e.g. a property whose
+ * range is `rdfs.Class` must point at a class, not an instance. This is the
+ * named-reference analogue of {@link EmbeddedKanonakTypeRule} (which constrains
+ * the declared type of an EMBEDDED value against its property's range).
+ *
+ * Reads the resolved object model (recursive on embeddeds at any depth): the
+ * property and its range are canonical URIs, the referent's nature is decided by
+ * `ResourceTypeClassifier`, identity by `uriMatches` — never by local-name range
+ * matching. Ordinary (non-meta) ranges and unresolved references are out of
+ * scope here (the latter is owned by `UnresolvedReferenceRule`); value-shape
+ * (scalar-vs-reference) is enforced structurally by the parser.
+ */
 export declare class ObjectPropertyValueValidationRule implements IRepositoryValidationRule {
-    private readonly standardProperties;
-    get ruleName(): string;
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    private scanEntityForObjectProperties;
-    private validateRangeType;
-    private buildPropertyMetadataAsync;
+    readonly ruleName = "ObjectPropertyValue";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
+    private walk;
+    private check;
+    private warn;
 }

package/dist/validation/rules/repository/PropertyDomainRule.d.ts

@@ -1,24 +1,28 @@
 import type { KanonakDocument } from '@kanonak-protocol/types/document/models/types';
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
-import type { ValidationCache } from '../../ValidationCache.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Every property used on an instance must be in scope for that instance's type:
+ * the property's `domain` must be the instance's type, an ancestor of it, or
+ * `rdfs.Resource` (which every resource is, so Resource-domain properties like
+ * `rdfs.label` apply universally). A property with no declared `domain` imposes
+ * no constraint.
+ *
+ * Reads the resolved object model (recursively, on embeddeds at any depth), NOT
+ * raw `document.body`: the predicate is the property's canonical URI, scope is
+ * the single canonical `superClassChain` walk, and domain membership is compared
+ * by `uriKey` identity — never by `lastIndexOf('.')` alias splitting or a
+ * local-name class-hierarchy map. Built-in predicates (`type`, `label`,
+ * `subClassOf`, …) are protocol-defined and skipped here. An unresolved
+ * predicate/property is reported by the dedicated predicate/reference rules.
+ */
 export declare class PropertyDomainRule implements IRepositoryValidationRule {
-    private readonly standardProperties;
-    get ruleName(): string;
+    readonly ruleName = "PropertyDomain";
     validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
-    /**
-       * Cache-driven hierarchy: union of `getClassDeclarations(docId)`
-       * across the document's transitive import closure. Each closure
-       * document's body is walked at most once per validation pass
-       * regardless of how many workspace documents share that closure
-       * member. Result shape matches `buildCompleteClassHierarchyAsync`
-       * so downstream `isTypeCompatibleWithDomain` works unchanged.
-       */
-    private buildClassHierarchyViaCache;
-    private buildCompleteClassHierarchyAsync;
-    private validateEntityProperties;
-    private isTypeCompatibleWithDomain;
-    private getPropertyValue;
-    private extractFirstValue;
+    private walk;
+    /** Check every non-built-in property used ON this node against its type's scope. */
+    private checkNode;
+    private error;
 }

package/dist/validation/rules/repository/PropertyHierarchyCycleRule.d.ts

@@ -2,10 +2,14 @@ import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/documen
 import type { KanonakDocument } from '@kanonak-protocol/types/document/models/types';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Detects a circular `subPropertyOf` hierarchy. Reads the resolved object model:
+ * the subPropertyOf graph is walked by canonical `KanonakUri` and compared by
+ * `uriKey` identity, so a cycle that closes across packages with differing alias
+ * spellings is caught, where the old local-name hierarchy map would miss it.
+ */
 export declare class PropertyHierarchyCycleRule implements IRepositoryValidationRule {
     readonly ruleName = "PropertyHierarchyCycle";
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    private buildPropertyHierarchy;
-    private detectCycle;
-    private detectCycleRecursive;
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
 }

package/dist/validation/rules/repository/PropertyKindRangeConsistencyRule.d.ts

@@ -0,0 +1,29 @@
+import type { KanonakDocument } from '@kanonak-protocol/types/document/models/types';
+import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
+import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
+import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * A property's declared KIND must match the NATURE of its range (#65 Gap A):
+ *
+ *   - `owl.DatatypeProperty` → a DATATYPE-valued range: an xsd type, `rdfs.Literal`,
+ *     or a datatype-derived class (e.g. `prose.Markdown`, declared `Datatype` and
+ *     ultimately `subClassOf` an xsd type).
+ *   - `owl.ObjectProperty` → a plain `rdfs.Class` range that is NOT datatype-derived.
+ *
+ * Without this the mismatch only surfaces LATE at resolution time ("value could
+ * not be resolved" when an object property tries to resolve literal text as a
+ * reference). The decision MUST be made by walking the range's `subClassOf`
+ * chain, because a datatype-derived class is datatype-valued even though
+ * `rdfs.Datatype` is itself a kind of `rdfs.Class` — a naive "is the range an
+ * `rdfs.Class`?" test gets it exactly backwards. "Datatype-valued" here means a
+ * chain node whose OWN type is `Datatype` (so xsd types and every datatype-
+ * derived class qualify) or `rdfs.Literal`; identity by `KanonakUri`, no
+ * hardcoded xsd-name set. An unresolved range is owned by
+ * `PropertyRangeReferenceRule`, a missing range by `PropertyRangeRequiredRule`.
+ */
+export declare class PropertyKindRangeConsistencyRule implements IRepositoryValidationRule {
+    readonly ruleName = "PropertyKindRangeConsistency";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
+    private error;
+}

package/dist/validation/rules/repository/PropertyRangeReferenceRule.d.ts

@@ -2,12 +2,19 @@ import type { KanonakDocument } from '@kanonak-protocol/types/document/models/ty
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Every Object/Datatype property `range` must resolve to a class-like resource:
+ * a Class, or a Datatype (core-xsd types — `string`, `integer`, … — and
+ * datatype-derived classes are all `type: Datatype` subjects). Reads the
+ * resolved object model: the range is a `ReferenceKanonak` resolved through the
+ * import closure (alias-agnostic), checked by `findSubjectByUri` +
+ * `ResourceTypeClassifier`, never by hardcoded primitive/built-in name sets or
+ * `split('.')` alias extraction. (Missing range is `PropertyRangeRequiredRule`.)
+ */
 export declare class PropertyRangeReferenceRule implements IRepositoryValidationRule {
-    private readonly builtInClasses;
-    private readonly primitiveTypes;
-    get ruleName(): string;
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    private isTypeAvailableInImports;
-    private isTypeAvailableInImportsRecursive;
-    private isValidRangeTargetType;
+    readonly ruleName = "PropertyRangeReference";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
+    private resolvesToClassLike;
+    private error;
 }

package/dist/validation/rules/repository/PropertyRangeRequiredRule.d.ts

@@ -2,7 +2,18 @@ import type { KanonakDocument } from '@kanonak-protocol/types/document/models/ty
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Every Object/Datatype property must declare a `range`. Reads the resolved
+ * object model: presence is tested by the `range` predicate's canonical URI
+ * (`hasProperty`), so the aliased `rdfs.range` form is recognised exactly like
+ * the bare `range` — fixing the alias-blind raw-dict check that keyed off the
+ * literal `'range'` dict key and falsely reported "must have a range" for a
+ * property authored with `rdfs.range:` (#65 Gap B). Whether the declared range
+ * actually RESOLVES is `PropertyRangeReferenceRule`'s concern.
+ */
 export declare class PropertyRangeRequiredRule implements IRepositoryValidationRule {
-    get ruleName(): string;
-    validateAsync(document: KanonakDocument, _repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
+    readonly ruleName = "PropertyRangeRequired";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
+    private error;
 }

package/dist/validation/rules/repository/SubClassOfReferenceRule.d.ts

@@ -2,18 +2,21 @@ import type { KanonakDocument } from '@kanonak-protocol/types/document/models/ty
 import type { IKanonakDocumentRepository } from '@kanonak-protocol/types/document/models';
 import type { IRepositoryValidationRule } from './IRepositoryValidationRule.js';
 import { OntologyValidationError } from '../../OntologyValidationError.js';
+import type { ValidationCache } from '../../ValidationCache.js';
+/**
+ * Every `subClassOf` target must resolve to a class-like resource. Per core-rdf
+ * (`Datatype subClassOf Class`) a Datatype is a Class, so datatype hierarchies
+ * (`xsd.integer subClassOf xsd.decimal`, `Markdown subClassOf SubstitutableString`)
+ * are well-formed — the target check accepts both.
+ *
+ * Reads the resolved object model: the parser turns each `subClassOf` value into
+ * a `ReferenceKanonak`, so the target is a `KanonakUri` resolved through the
+ * import closure (alias-agnostic) and existence is checked by `findSubjectByUri`,
+ * never by a hardcoded built-in-name list or `split('.')` alias extraction.
+ */
 export declare class SubClassOfReferenceRule implements IRepositoryValidationRule {
-    private readonly builtInClasses;
-    get ruleName(): string;
-    /**
-     * A valid `subClassOf` target is anything that is a Class — and per
-     * core-rdf's `Datatype subClassOf Class`, a Datatype is a Class. So
-     * datatype hierarchies (`xsd.integer subClassOf xsd.decimal`,
-     * `Markdown subClassOf SubstitutableString`) are well-formed and the
-     * target check must accept both `Class` and `Datatype` (aliased or not).
-     */
-    private isClassLikeType;
-    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository): Promise<OntologyValidationError[]>;
-    private isClassAvailableInImports;
-    private isClassAvailableInImportsRecursive;
+    readonly ruleName = "SubClassOfReference";
+    validateAsync(document: KanonakDocument, repository: IKanonakDocumentRepository, cache?: ValidationCache): Promise<OntologyValidationError[]>;
+    private resolvesToClassLike;
+    private error;
 }