# Retrieval Index Schema: `info-tech-canon.retrieval-index.v1` Infospace: `canon` Items: **81** ## Common Distinctions - **Agentic fallback vs direct functional interface**: Use cross-repository agentic work to interpret novel demand; use an owned API, CLI, or MCP surface when the outcome is stable and recurring. Sources: `practice-pattern/agentic-drives-functional` - **Interface deprecation vs retirement vs removal**: Deprecation guides and observes callers, retirement ends legacy behavior while retaining a metered tombstone, and removal deletes that tombstone only after the evidence gate passes. Sources: `practice-pattern/interface-deprecation-strangler` - **Actor vs Subject vs Principal**: Use actor for the acting entity in a context, subject for the entity a policy evaluates, and principal for the authenticated identity bound to access decisions. Sources: `model/organization`, `model/access-control`, `standard/caring` - **Organization Role vs AccessRole vs CARING role**: Organization roles describe responsibility or position; access roles describe permissions; CARING roles classify access-governance needs and analysis. Sources: `model/organization`, `model/access-control`, `standard/caring` - **Policy vs Control vs Evidence**: Governance owns policy and control; ITC-EVID owns the distinct evidence assertion and its addressable source. Evidence supports a stated interest without guaranteeing truth. Sources: `model/governance`, `model/evidence`, `model/security`, `model/observability` - **Intent vs Scope vs Purpose**: Intent captures why a producer or consumer exists, scope bounds producer ownership and promises, and purpose captures consumer demand anchored in consumer intent. Sources: `kernel/itc-core`, `model/purpose-demand-extension`, `pattern/intent-scope-purposes`, `profile/small-saas` ## Items ### Canon federation research provenance - ID: `assimilation/canon-federation` - Kind: `assimilation` - Canonical path: `assimilation/canon-federation/ASSIMILATION.md` - Source path: `infospace/assimilation/canon-federation/source/research/CorpusIndex.md` - Summary: Canon artifact: Canon federation research provenance. - Imports and anchors: `concept-area/family`, `model/access-control`, `model/evidence`, `model/identity`, `model/organization` - Owned concepts: `Canon federation research provenance` ### Assimilation — EmissionCadenceDeclaration handover - ID: `assimilation/emission-cadence` - Kind: `assimilation` - Canonical path: `assimilation/emission-cadence/ASSIMILATION.md` - Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md` - Summary: Canon artifact: Assimilation — EmissionCadenceDeclaration handover. - Imports and anchors: `kernel/itc-core` - Owned concepts: `Assimilation — EmissionCadenceDeclaration handover` ### Assimilation — IT Capability Canon (ITCC) v0.1 - ID: `assimilation/it-capability-canon` - Kind: `assimilation` - Canonical path: `assimilation/it-capability-canon/ASSIMILATION.md` - Source path: `infospace/assimilation/it-capability-canon/source/ITCapabilityCanonV0.1.md` - Summary: Canon artifact: Assimilation — IT Capability Canon (ITCC) v0.1. - Imports and anchors: `kernel/itc-core` - Owned concepts: `Assimilation — IT Capability Canon (ITCC) v0.1` ### CARING Kubernetes RBAC Benchmark - ID: `benchmark/caring/kubernetes-rbac` - Kind: `benchmark-workspace` - Canonical path: `standards/caring/benchmarks/kubernetes-rbac/benchmark.yaml` - Source path: `infospace/standards/caring/benchmarks/kubernetes-rbac/benchmark.yaml` - Summary: Benchmark workspace definition and review criteria: CARING Kubernetes RBAC Benchmark. - Imports and anchors: `standard/caring`, `standard/tagging` - Owned concepts: `CARING Kubernetes RBAC Benchmark` ### Kubernetes RBAC CARING Access Descriptors - ID: `benchmark/caring/kubernetes-rbac/access-descriptors` - Kind: `access-descriptor-set` - Canonical path: `standards/caring/benchmarks/kubernetes-rbac/access-descriptors.yaml` - Source path: `infospace/standards/caring/benchmarks/kubernetes-rbac/access-descriptors.yaml` - Summary: Structured CARING access descriptor set: Kubernetes RBAC CARING Access Descriptors. - Imports and anchors: `model/access-control`, `model/devsecops`, `model/security`, `standard/caring` - Owned concepts: `Kubernetes RBAC CARING Access Descriptors` ### Kubernetes RBAC To CARING Mapping - ID: `benchmark/caring/kubernetes-rbac/caring-mapping` - Kind: `caring-mapping` - Canonical path: `standards/caring/benchmarks/kubernetes-rbac/caring-mapping.yaml` - Source path: `infospace/standards/caring/benchmarks/kubernetes-rbac/caring-mapping.yaml` - Summary: Native access model to CARING mapping: Kubernetes RBAC To CARING Mapping. - Imports and anchors: none - Owned concepts: `Kubernetes RBAC To CARING Mapping` ### Kubernetes RBAC Benchmark Findings And Canon Pressure - ID: `benchmark/caring/kubernetes-rbac/findings` - Kind: `benchmark-findings` - Canonical path: `standards/caring/benchmarks/kubernetes-rbac/findings-and-canon-pressure.yaml` - Source path: `infospace/standards/caring/benchmarks/kubernetes-rbac/findings-and-canon-pressure.yaml` - Summary: Benchmark findings, gaps, and canon pressure: Kubernetes RBAC Benchmark Findings And Canon Pressure. - Imports and anchors: none - Owned concepts: `Kubernetes RBAC Benchmark Findings And Canon Pressure` ### Kubernetes RBAC Native Concept Map - ID: `benchmark/caring/kubernetes-rbac/native-concepts` - Kind: `native-concept-map` - Canonical path: `standards/caring/benchmarks/kubernetes-rbac/native-concepts.yaml` - Source path: `infospace/standards/caring/benchmarks/kubernetes-rbac/native-concepts.yaml` - Summary: Native source concept map for assimilation or benchmark work: Kubernetes RBAC Native Concept Map. - Imports and anchors: none - Owned concepts: `Kubernetes RBAC Native Concept Map` ### InfoTechCanon Capability Catalog - ID: `capability-catalog/itc-cap` - Kind: `capability-catalog` - Canonical path: `models/capability/capabilities.yaml` - Source path: `infospace/assimilation/it-capability-canon/source/capabilities.yaml` - Summary: Canon artifact: InfoTechCanon Capability Catalog. - Imports and anchors: none - Owned concepts: `InfoTechCanon Capability Catalog` ### InfoTechCanon Attribute Value Type Catalog - ID: `catalog/attribute-value-types` - Kind: `concept-catalog` - Canonical path: `models/data/attribute-value-types.yaml` - Source path: `demand/AttributeValueTypes.md` - Summary: Structured candidate concept catalog: InfoTechCanon Attribute Value Type Catalog. - Imports and anchors: none - Owned concepts: `InfoTechCanon Attribute Value Type Catalog` ### InfoTechCanon Evidence Basis Catalog - ID: `catalog/evidence-basis` - Kind: `concept-catalog` - Canonical path: `models/governance/evidence-basis.yaml` - Source path: `demand/EvidenceBasis.md` - Summary: Structured candidate concept catalog: InfoTechCanon Evidence Basis Catalog. - Imports and anchors: none - Owned concepts: `InfoTechCanon Evidence Basis Catalog` ### Repo Scoping Canon Benefit Analysis - ID: `comparison/repo-scoping/canon-benefit-analysis` - Kind: `benefit-analysis` - Canonical path: `evaluations/repo-scoping/canon-benefit-analysis.yaml` - Source path: `infospace/evaluations/repo-scoping/canon-benefit-analysis.yaml` - Summary: Consumer benefit analysis against canon surfaces: Repo Scoping Canon Benefit Analysis. - Imports and anchors: none - Owned concepts: `Repo Scoping Canon Benefit Analysis` ### Repo Scoping Consumer Workplan Brief - ID: `comparison/repo-scoping/consumer-workplan-brief` - Kind: `consumer-workplan-brief` - Canonical path: `evaluations/repo-scoping/consumer-workplan-brief.md` - Source path: `infospace/evaluations/repo-scoping/consumer-workplan-brief.md` - Summary: Consumer repo workplan seed brief: Repo Scoping Consumer Workplan Brief. - Imports and anchors: `model/purpose-demand-extension` - Owned concepts: `Repo Scoping Consumer Workplan Brief` ### Repo Scoping Canon Extension Candidates - ID: `comparison/repo-scoping/extension-candidates` - Kind: `extension-candidate-set` - Canonical path: `evaluations/repo-scoping/extension-candidates.yaml` - Source path: `infospace/evaluations/repo-scoping/extension-candidates.yaml` - Summary: Reviewable canon extension candidate set: Repo Scoping Canon Extension Candidates. - Imports and anchors: none - Owned concepts: `Repo Scoping Canon Extension Candidates` ### Repo Scoping Canon Comparison Frame - ID: `comparison/repo-scoping/frame` - Kind: `comparison-frame` - Canonical path: `evaluations/repo-scoping/comparison-frame.yaml` - Source path: `infospace/evaluations/repo-scoping/comparison-frame.yaml` - Summary: Structured comparison questions and domains: Repo Scoping Canon Comparison Frame. - Imports and anchors: `model/governance`, `model/purpose-demand-extension`, `model/task` - Owned concepts: `Repo Scoping Canon Comparison Frame` ### Repo Scoping Canon Comparison Report - ID: `comparison/repo-scoping/report` - Kind: `comparison-report` - Canonical path: `evaluations/repo-scoping/comparison-report.md` - Source path: `infospace/evaluations/repo-scoping/comparison-report.md` - Summary: Canon-side comparison report: Repo Scoping Canon Comparison Report. - Imports and anchors: `model/governance`, `model/information-space`, `model/task`, `pattern/intent-scope-purposes` - Owned concepts: `Repo Scoping Canon Comparison Report` ### Family concept-area seed - ID: `concept-area/family` - Kind: `concept-area-seed` - Canonical path: `concepts/family/FamilySeed.md` - Source path: `../prj-canon-federation/ledger/concept-ownership.json` - Summary: Canon artifact: Family concept-area seed. - Imports and anchors: `kernel/itc-core`, `model/organization` - Owned concepts: `Family`, `Family concept-area seed` ### Purpose And Consumer Demand Concept Catalog - ID: `concept-catalog/purpose-demand` - Kind: `concept-catalog` - Canonical path: `concepts/purpose-demand.yaml` - Source path: `infospace/concepts/purpose-demand.yaml` - Summary: Structured candidate concept catalog: Purpose And Consumer Demand Concept Catalog. - Imports and anchors: `kernel/itc-core`, `model/governance` - Owned concepts: `Purpose And Consumer Demand Concept Catalog` ### Railiance Fabric Canon Conformance Pack - ID: `conformance/railiance-fabric` - Kind: `conformance-pack` - Canonical path: `evaluations/railiance-fabric/conformance-pack.yaml` - Source path: `infospace/evaluations/railiance-fabric/conformance-pack.yaml` - Summary: Machine-readable canon-side conformance support pack: Railiance Fabric Canon Conformance Pack. - Imports and anchors: `model/data`, `model/devsecops`, `model/governance`, `model/landscape`, `model/network`, `model/observability`, `model/purpose-demand-extension`, `model/security`, `model/task`, `standard/tagging` - Owned concepts: `Railiance Fabric Canon Conformance Pack` ### Railiance Fabric Consumer Workplan Brief - ID: `conformance/railiance-fabric/consumer-workplan-brief` - Kind: `consumer-workplan-brief` - Canonical path: `evaluations/railiance-fabric/consumer-workplan-brief.md` - Source path: `infospace/evaluations/railiance-fabric/consumer-workplan-brief.md` - Summary: Consumer repo workplan seed brief: Railiance Fabric Consumer Workplan Brief. - Imports and anchors: `model/purpose-demand-extension` - Owned concepts: `Railiance Fabric Consumer Workplan Brief` ### Railiance Fabric Entity And Edge Capture Criteria - ID: `conformance/railiance-fabric/entity-edge-capture-criteria` - Kind: `capture-criteria` - Canonical path: `evaluations/railiance-fabric/entity-edge-capture-criteria.yaml` - Source path: `infospace/evaluations/railiance-fabric/entity-edge-capture-criteria.yaml` - Summary: Criteria for canonical entity and edge capture: Railiance Fabric Entity And Edge Capture Criteria. - Imports and anchors: `model/data`, `model/devsecops`, `model/governance`, `model/landscape`, `model/network`, `model/observability`, `model/purpose-demand-extension`, `model/security`, `model/task` - Owned concepts: `Railiance Fabric Entity And Edge Capture Criteria` ### Railiance Fabric Mapping Expectations - ID: `conformance/railiance-fabric/mapping-expectations` - Kind: `mapping-expectation` - Canonical path: `evaluations/railiance-fabric/mapping-expectations.yaml` - Source path: `infospace/evaluations/railiance-fabric/mapping-expectations.yaml` - Summary: Expected mappings between consumer graph capture and canon surfaces: Railiance Fabric Mapping Expectations. - Imports and anchors: none - Owned concepts: `Railiance Fabric Mapping Expectations` ### Railiance Fabric Visualization Examples - ID: `conformance/railiance-fabric/visualization-examples` - Kind: `visualization-example-set` - Canonical path: `evaluations/railiance-fabric/visualization-examples.yaml` - Source path: `infospace/evaluations/railiance-fabric/visualization-examples.yaml` - Summary: Graph visualization examples and bad-shape corrections: Railiance Fabric Visualization Examples. - Imports and anchors: none - Owned concepts: `Railiance Fabric Visualization Examples` ### User Engine Canon Evaluation Pack - ID: `evaluation/user-engine` - Kind: `evaluation-pack` - Canonical path: `evaluations/user-engine/evaluation-pack.yaml` - Source path: `infospace/evaluations/user-engine/evaluation-pack.yaml` - Summary: Machine-readable canon-side evaluation pack: User Engine Canon Evaluation Pack. - Imports and anchors: `model/access-control`, `model/data`, `model/governance`, `model/organization`, `model/purpose-demand-extension`, `model/security`, `model/task`, `standard/caring` - Owned concepts: `User Engine Canon Evaluation Pack` ### User Engine Consumer Workplan Brief - ID: `evaluation/user-engine/consumer-workplan-brief` - Kind: `consumer-workplan-brief` - Canonical path: `evaluations/user-engine/consumer-workplan-brief.md` - Source path: `infospace/evaluations/user-engine/consumer-workplan-brief.md` - Summary: Consumer repo workplan seed brief: User Engine Consumer Workplan Brief. - Imports and anchors: `model/purpose-demand-extension` - Owned concepts: `User Engine Consumer Workplan Brief` ### User Engine Canon Interface Card Expectations - ID: `evaluation/user-engine/interface-card-expectations` - Kind: `interface-card-expectation` - Canonical path: `evaluations/user-engine/interface-card-expectations.yaml` - Source path: `infospace/evaluations/user-engine/interface-card-expectations.yaml` - Summary: Expected Canon Interface Card fields and mappings: User Engine Canon Interface Card Expectations. - Imports and anchors: `model/purpose-demand-extension`, `standard/caring` - Owned concepts: `User Engine Canon Interface Card Expectations` ### User Engine Canon Evaluation Questions - ID: `evaluation/user-engine/questions` - Kind: `evaluation-question-set` - Canonical path: `evaluations/user-engine/questions.yaml` - Source path: `infospace/evaluations/user-engine/questions.yaml` - Summary: Structured canon evaluation question set: User Engine Canon Evaluation Questions. - Imports and anchors: `model/access-control`, `model/data`, `model/governance`, `model/organization`, `model/purpose-demand-extension`, `model/security`, `model/task` - Owned concepts: `User Engine Canon Evaluation Questions` ### User Engine Small SaaS Alignment Lens - ID: `evaluation/user-engine/small-saas-alignment` - Kind: `profile-alignment` - Canonical path: `evaluations/user-engine/small-saas-alignment.yaml` - Source path: `infospace/evaluations/user-engine/small-saas-alignment.yaml` - Summary: Profile-specific evaluation alignment artifact: User Engine Small SaaS Alignment Lens. - Imports and anchors: `model/access-control`, `model/governance`, `model/organization` - Owned concepts: `User Engine Small SaaS Alignment Lens` ### Canon-Side Consumer Purpose Portfolio - ID: `example/consumer-purpose-portfolio` - Kind: `example` - Canonical path: `examples/consumer-purpose-portfolio.yaml` - Source path: `infospace/examples/consumer-purpose-portfolio.yaml` - Summary: Canon-side example artifact: Canon-Side Consumer Purpose Portfolio. - Imports and anchors: `profile/small-saas` - Owned concepts: `Canon-Side Consumer Purpose Portfolio` ### Qonto Assistant Emission Cadence Worked Example - ID: `example/emission-cadence/qonto-assistant` - Kind: `example` - Canonical path: `standards/emission-cadence/examples/qonto-assistant.yaml` - Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md` - Summary: Canon-side example artifact: Qonto Assistant Emission Cadence Worked Example. - Imports and anchors: `standard/emission-cadence` - Owned concepts: `Qonto Assistant Emission Cadence Worked Example` ### InfoTechCanon federation interface - ID: `interface-card/canon-federation` - Kind: `interface-card` - Canonical path: `interfaces/federation.yaml` - Source path: `../the-custodian/canon/architecture/adr-006-canon-federation-concept-ownership.md` - Summary: Canon artifact: InfoTechCanon federation interface. - Imports and anchors: `kernel/itc-core` - Owned concepts: `InfoTechCanon federation interface` ### InfoTechCanon Core - ID: `kernel/itc-core` - Kind: `kernel` - Canonical path: `kernel/InfoTechCanonCore.md` - Source path: `seeds/InfoTechCanonCore_RC1_seed.md` - Summary: Kernel artifact that defines canon structure or integration: InfoTechCanon Core. - Imports and anchors: none - Owned concepts: `Activity`, `AgentBrief`, `AgentReference`, `Alias`, `Ambiguity`, `Assimilation`, `CanonArtifact`, `CanonInterfaceCard`, `Canonical Owner`, `ChangeRecord`, `Concept`, `Conflict`, `ConformanceLevel`, `DecisionRecord`, `Drift`, `ExternalReference`, `Gap`, `Import`, `Influence`, `InfoTechCanon Core`, `Label`, `Mapping`, `Namespace`, `OpenQuestion`, `Overlap`, `Pattern`, `ProvenanceRecord`, `RelationshipDefinition`, `Source`, `Standard`, `ValidationResult`, `ValidationRule`, `Version`, `VersionRecord` ### InfoTechCanon Kernel Map - ID: `kernel/itc-kernel-map` - Kind: `kernel` - Canonical path: `kernel/InfoTechCanonKernelMap.md` - Source path: `seeds/InfoTechCanonKernelMap_RC1.md` - Summary: Kernel artifact that defines canon structure or integration: InfoTechCanon Kernel Map. - Imports and anchors: none - Owned concepts: `InfoTechCanon Kernel Map` ### ITC-CAP concept mappings to anchoring canon models - ID: `mapping/capability-anchors` - Kind: `mapping` - Canonical path: `mappings/capability-anchors.yaml` - Source path: `infospace/assimilation/it-capability-canon/mappings.yaml` - Summary: Mapping artifact connecting canon surfaces: ITC-CAP concept mappings to anchoring canon models. - Imports and anchors: none - Owned concepts: `ITC-CAP concept mappings to anchoring canon models` ### Emission cadence handover mappings - ID: `mapping/emission-cadence-handover` - Kind: `mapping` - Canonical path: `assimilation/emission-cadence/mappings.yaml` - Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md` - Summary: Mapping artifact connecting canon surfaces: Emission cadence handover mappings. - Imports and anchors: none - Owned concepts: `Emission cadence handover mappings` ### Purpose Demand Governance Extension Candidates - ID: `mapping/purpose-demand-governance-candidates` - Kind: `mapping` - Canonical path: `mappings/purpose-demand-governance-candidates.yaml` - Source path: `infospace/mappings/purpose-demand-governance-candidates.yaml` - Summary: Mapping artifact connecting canon surfaces: Purpose Demand Governance Extension Candidates. - Imports and anchors: `model/task` - Owned concepts: `Purpose Demand Governance Extension Candidates` ### InfoTechCanon Access Control Model - ID: `model/access-control` - Kind: `model` - Canonical path: `models/access-control/InfoTechCanonAccessControlModel.md` - Source path: `seeds/InfoTechCanonAccessControlModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Access Control Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/governance`, `model/identity`, `model/organization` - Owned concepts: `AccessCertification`, `AccessControlEntity`, `AccessFinding`, `AccessRemediation`, `AccessReview`, `AccessRole`, `AccessSession`, `AgentAccess`, `AuthenticatedSubject`, `AuthenticationStrengthReference`, `AuthorizationDecision`, `AuthorizationRequest`, `BreakGlassAccess`, `Condition`, `CredentialReference`, `DecisionReason`, `DelegatedAccess`, `Denial`, `Entitlement`, `EvaluationContext`, `ExcessAccess`, `Grant`, `IdentityReference`, `InfoTechCanon Access Control Model`, `JustInTimeAccess`, `Operation`, `OrphanedAccess`, `Permission`, `PolicyAdministrationPoint`, `PolicyBinding`, `PolicyDecisionPoint`, `PolicyEnforcementPoint`, `PolicyInformationPoint`, `PolicyRetrievalPoint`, `Principal`, `Privilege`, `ProtectedResource`, `RelationshipTuple`, `Resource`, `ResourceAction`, `ResourceScope`, `RoleBinding`, `ServiceAccountAccess`, `StaleAccess`, `Subject`, `TemporaryAccess`, `TokenReference` ### InfoTechCanon Capability Model - ID: `model/capability` - Kind: `model` - Canonical path: `models/capability/InfoTechCanonCapabilityModel.md` - Source path: `infospace/assimilation/it-capability-canon/source/ITCapabilityCanonV0.1.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Capability Model. - Imports and anchors: `catalog/evidence-basis`, `kernel/itc-core`, `model/evidence`, `model/governance`, `model/landscape`, `model/observability`, `model/purpose-demand-extension` - Owned concepts: `Capability`, `CapabilityConsumption`, `CapabilityContract`, `CapabilityDomain`, `CapabilityEvidenceHook`, `CapabilityInclusionRule`, `CapabilityMaturityLevel`, `CapabilityProfile`, `CapabilityProvider`, `CapabilityProvision`, `CapabilityQualityDimension`, `CapabilityRequirement`, `CapabilityResourceClass`, `Capacity behaviour`, `InfoTechCanon Capability Model`, `Supply` ### InfoTechCanon Data Model - ID: `model/data` - Kind: `model` - Canonical path: `models/data/InfoTechCanonDataModel.md` - Source path: `seeds/InfoTechCanonDataModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Data Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/governance` - Owned concepts: `Attribute`, `AttributeValueType`, `BreakingChange`, `BusinessTerm`, `CodeList`, `CompatibilityRule`, `Constraint`, `ConsumerExpectation`, `DataAccessPattern`, `DataAvailability`, `DataCategory`, `DataClassification`, `DataContract`, `DataDefinition`, `DataDistribution`, `DataDomain`, `DataElement`, `DataElementConcept`, `DataEntity`, `DataFlow`, `DataFreshness`, `DataLineage`, `DataObject`, `DataProduct`, `DataQualityCheck`, `DataQualityDimension`, `DataQualityIssue`, `DataQualityResult`, `DataQualityRule`, `DataResidency`, `DataService`, `DataStoreReference`, `DataSubjectCategory`, `DataType`, `DataUsageConstraint`, `Dataset`, `DatasetSeries`, `Derivation`, `Field`, `FitnessForUse`, `GlossaryTerm`, `InfoTechCanon Data Model`, `MasterDataReference`, `ProcessingPurpose`, `ProducerExpectation`, `Record`, `ReferenceData`, `Representation`, `RetentionRuleReference`, `SchemaEvolutionPolicy`, `Sensitivity`, `Transformation` ### InfoTechCanon DevSecOps Model - ID: `model/devsecops` - Kind: `model` - Canonical path: `models/devsecops/InfoTechCanonDevSecOpsModel.md` - Source path: `seeds/InfoTechCanonDevSecOpsModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon DevSecOps Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/security` - Owned concepts: `AgentExecutionEvidence`, `AgentGeneratedPatch`, `AgentReview`, `Artifact`, `ArtifactDigest`, `ArtifactVersion`, `Attestation`, `Branch`, `ChangeFailure`, `CodeReview`, `CodingAgentChange`, `Commit`, `ContainerImage`, `DeliveryMetric`, `DeploymentExecution`, `DeploymentHealthSignal`, `DeploymentManifest`, `DeploymentPlan`, `DeploymentRecord`, `DeploymentVerification`, `DevSecOpsEntity`, `EnvironmentPromotion`, `FeedbackLoop`, `GateDecision`, `HumanSupervisionReference`, `IaCModule`, `InfoTechCanon DevSecOps Model`, `Package`, `Pipeline`, `PipelineDefinition`, `PipelineIdentity`, `PipelineJob`, `PipelineResult`, `PipelineRun`, `PipelineStage`, `PipelineStep`, `PolicyGate`, `Promotion`, `Provenance`, `PullRequest`, `QualityGate`, `RecoveryAction`, `Release`, `ReleaseApprovalReference`, `ReleaseCandidate`, `ReleaseNote`, `ReleaseVersion`, `Repository`, `Rollback`, `RolloutStrategy`, `Runner`, `ScanResult`, `ScanRun`, `Signature`, `Software Bill of Materials`, `SourceChange`, `SourceTag`, `SupplyChainEvidence`, `TestResult`, `TestRun`, `TransparencyLogEntry`, `VEXReference`, `VerificationEvidence` ### InfoTechCanon Evidence Model - ID: `model/evidence` - Kind: `model` - Canonical path: `models/evidence/InfoTechCanonEvidenceModel.md` - Source path: `../prj-canon-federation/ledger/concept-ownership.json` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Evidence Model. - Imports and anchors: `kernel/itc-core` - Owned concepts: `Adjudication Outcome`, `Evidence`, `Evidence Source`, `Evidence strength`, `InfoTechCanon Evidence Model` ### InfoTechCanon Governance Model - ID: `model/governance` - Kind: `model` - Canonical path: `models/governance/InfoTechCanonGovernanceModel.md` - Source path: `seeds/InfoTechCanonGovernanceModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Governance Model. - Imports and anchors: `kernel/itc-core`, `model/evidence` - Owned concepts: `Approval`, `Assertion`, `Assessment`, `AssuranceCase`, `AssuranceConclusion`, `Audit`, `CompensatingControl`, `ComplianceRequirement`, `Control`, `ControlActivity`, `ControlImplementation`, `ControlObjective`, `ControlResult`, `ControlTest`, `Decision`, `DecisionRight`, `Escalation`, `EvidenceBasis`, `Exception`, `Finding`, `GovernanceCycle`, `GovernanceEntity`, `GovernanceForum`, `GovernanceProcess`, `GovernanceScope`, `GovernanceSystem`, `Guideline`, `Impact`, `InfoTechCanon Governance Model`, `Likelihood`, `Nonconformity`, `Obligation`, `Policy`, `Principle`, `RegulatoryReference`, `Remediation`, `Requirement`, `Review`, `Risk`, `RiskAcceptance`, `RiskSource`, `RiskTreatment`, `Rule`, `Waiver` ### InfoTechCanon Identity Model - ID: `model/identity` - Kind: `model` - Canonical path: `models/identity/InfoTechCanonIdentityModel.md` - Source path: `../prj-canon-federation/ledger/concept-ownership.json` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Identity Model. - Imports and anchors: `kernel/itc-core`, `model/access-control`, `model/evidence`, `model/organization` - Owned concepts: `Account`, `Administration Relationship`, `Affiliation Relationship`, `Assurance Level`, `Claim`, `Credential`, `Delegation Relationship`, `Following Relationship`, `Identifier`, `Identity Record`, `InfoTechCanon Identity Model`, `Lifecycle State`, `Persona`, `Profile`, `Pseudonymous Identifier`, `Realm`, `Relationship`, `Representation Relationship`, `Scope`, `Scoped Identifier`, `Service Account`, `Synonymity Assertion`, `Tenant`, `Trust Relationship` ### InfoTechCanon Information Space Model - ID: `model/information-space` - Kind: `model` - Canonical path: `models/information-space/InfoTechCanonInformationSpaceModel.md` - Source path: `seeds/InfoTechCanonInformationSpaceModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Information Space Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/identity` - Owned concepts: `Anchor`, `AssimilationReport`, `Backlink`, `Block`, `BrokenLink`, `Chunk`, `Citation`, `Collection`, `ConceptIndex`, `ConceptPage`, `ConflictingDefinition`, `Corpus`, `CrossReference`, `DependencyReference`, `Document`, `DuplicateContent`, `EmbeddingRecord`, `Excerpt`, `FrontMatter`, `Generation`, `GraphView`, `Heading`, `Index`, `InfoTechCanon Information Space Model`, `InformationSpace`, `Infospace`, `KnowledgeArtifact`, `KnowledgeBase`, `Link`, `LowRetrievalQuality`, `MapView`, `MappingDocument`, `MappingReference`, `MarkdownDocument`, `MetadataRecord`, `MissingMetadata`, `NavigationView`, `OrphanArtifact`, `PatternDocument`, `ProfileDocument`, `RelationshipIndex`, `RepositorySpace`, `RetrievalContext`, `RetrievalEvaluation`, `RetrievalQuery`, `RetrievalResult`, `RetrievalUnit`, `ReviewRecord`, `Revision`, `SearchIndex`, `Section`, `Shard`, `SourceReference`, `StaleContent`, `StandardDocument`, `Status`, `Summary`, `TopicIndex`, `UsePath`, `VectorIndex` ### InfoTechCanon Landscape Model - ID: `model/landscape` - Kind: `model` - Canonical path: `models/landscape/InfoTechCanonLandscapeModel.md` - Source path: `seeds/InfoTechCanonLandscapeModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Landscape Model. - Imports and anchors: `kernel/itc-core`, `model/evidence` - Owned concepts: `ApplicationService`, `BusinessService`, `Environment`, `InfoTechCanon Landscape Model`, `LandscapeClaim`, `LandscapeEntity`, `LandscapeEvidence`, `LandscapeRelationship`, `LandscapeSource`, `LandscapeState`, `RuntimeResource`, `SoftwareComponent`, `SoftwareSystem`, `TechnicalService`, `Workload` ### InfoTechCanon Network Model - ID: `model/network` - Kind: `model` - Canonical path: `models/network/InfoTechCanonNetworkModel.md` - Source path: `seeds/InfoTechCanonNetworkModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Network Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/security` - Owned concepts: `ACL`, `AddressFamily`, `AllowedFlow`, `AppliedNetworkState`, `AssessedNetworkState`, `AttackSurfaceReference`, `Circuit`, `ConnectivityService`, `DNSRecord`, `DNSZone`, `DeclaredNetworkState`, `DeniedFlow`, `EgressEndpoint`, `Endpoint`, `Firewall`, `FirewallRule`, `Gateway`, `HistoricalNetworkState`, `Hostname`, `IPAddress`, `IPAllocation`, `InfoTechCanon Network Model`, `IngressEndpoint`, `IntendedNetworkState`, `Interface`, `KubernetesNetworkPolicy`, `LoadBalancer`, `ManagementEndpoint`, `Microsegment`, `NAT`, `NetworkACL`, `NetworkConfiguration`, `NetworkDevice`, `NetworkDomain`, `NetworkEntity`, `NetworkFabric`, `NetworkFlow`, `NetworkIntent`, `NetworkNode`, `NetworkPolicy`, `NetworkRegion`, `NetworkSegment`, `NetworkSite`, `NetworkTenant`, `NetworkZone`, `NextHop`, `ObservedFlow`, `ObservedNetworkState`, `OverlayNetwork`, `Path`, `Peering`, `Port`, `Prefix`, `PrivateEndpoint`, `Proxy`, `PublicEndpoint`, `ReachabilityClaim`, `ReachabilityTest`, `ReconciliationResult`, `Route`, `RouteTable`, `Router`, `SecurityGroup`, `SecurityZone`, `ServiceEndpoint`, `ServiceMeshPolicy`, `ServiceName`, `Subnet`, `Switch`, `TerminationPoint`, `TrafficPolicy`, `TrustZoneReference`, `UnderlayNetwork`, `VLAN`, `VRF`, `WorkloadEndpoint` ### InfoTechCanon Observability Model - ID: `model/observability` - Kind: `model` - Canonical path: `models/observability/InfoTechCanonObservabilityModel.md` - Source path: `seeds/InfoTechCanonObservabilityModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Observability Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/task` - Owned concepts: `Alert`, `AlertCorrelation`, `AlertRoute`, `AlertRule`, `AlertSuppression`, `Annotation`, `AvailabilityWindow`, `Baggage`, `BurnRate`, `Correlation`, `Counter`, `Dashboard`, `ErrorBudget`, `EscalationReference`, `Event`, `EventConsumer`, `EventCorrelationKey`, `EventEnvelope`, `EventSource`, `EventType`, `Exemplar`, `Gauge`, `HealthState`, `Histogram`, `InfoTechCanon Observability Model`, `Log`, `LogContext`, `LogLevel`, `LogRecord`, `LogStream`, `Metric`, `MetricInstrument`, `MetricPoint`, `Notification`, `ObservabilityEntity`, `ObservabilityEvidence`, `ObservedIncident`, `ObservedResource`, `OperationalView`, `PerformanceProfile`, `PostIncidentObservation`, `ProfilingSample`, `Query`, `QueryResult`, `ResourceAttribute`, `ResourceProfile`, `RootCauseHypothesis`, `Runbook`, `SLAReference`, `Service Level Indicator`, `Service Level Objective`, `Signal`, `SignalSource`, `Snapshot`, `Span`, `SpanEvent`, `SpanLink`, `Telemetry`, `TelemetryPipeline`, `TelemetrySource`, `TimeSeries`, `Timeline`, `Trace`, `TraceContext`, `TraceSample` ### InfoTechCanon Organization Model - ID: `model/organization` - Kind: `model` - Canonical path: `models/organization/InfoTechCanonOrganizationModel.md` - Source path: `seeds/InfoTechCanonOrganizationModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Organization Model. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/identity` - Owned concepts: `Accountability`, `Actor`, `Agent`, `Assignment`, `Authority`, `Availability`, `Capacity`, `CollectiveActor`, `Community`, `Competence`, `Group`, `Household`, `InfoTechCanon Organization Model`, `Membership`, `Organization`, `OrganizationEntity`, `OrganizationalCapability`, `OrganizationalUnit`, `Ownership`, `Person`, `Position`, `Post`, `ReportingLine`, `Responsibility`, `Role`, `Skill`, `Stewardship`, `Team` ### InfoTechCanon Purpose And Demand Model Extension - ID: `model/purpose-demand-extension` - Kind: `model-extension` - Canonical path: `models/governance/InfoTechCanonPurposeDemandExtension.md` - Source path: `infospace/models/governance/InfoTechCanonPurposeDemandExtension.md` - Summary: Candidate extension to an existing canon model: InfoTechCanon Purpose And Demand Model Extension. - Imports and anchors: `kernel/itc-core`, `model/information-space`, `model/task` - Owned concepts: `ConsumerNeed`, `ConsumerPurpose`, `DemandSignal`, `EvolutionRequest`, `InfoTechCanon Purpose And Demand Model Extension`, `ProducerCapability`, `Purpose`, `PurposeFit`, `ScopePressure`, `UseCase` ### InfoTechCanon Security Model - ID: `model/security` - Kind: `model` - Canonical path: `models/security/InfoTechCanonSecurityModel.md` - Source path: `seeds/InfoTechCanonSecurityModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Security Model. - Imports and anchors: `kernel/itc-core`, `model/access-control`, `model/evidence` - Owned concepts: `AttackImpact`, `AttackPath`, `AttackPattern`, `AttackPrecondition`, `AttackStep`, `AttackTechnique`, `BlastRadius`, `ChokePoint`, `CompensatingMeasure`, `Containment`, `DataSecurityFinding`, `Detection`, `DetectionCoverage`, `DetectionRule`, `Eradication`, `Exploit`, `ExploitLikelihood`, `Exploitability`, `Exposure`, `ExposureFinding`, `HardeningMeasure`, `IdentityFinding`, `InfoTechCanon Security Model`, `Investigation`, `LessonLearned`, `Misconfiguration`, `MisconfigurationFinding`, `Mitigation`, `PenTestFinding`, `ProtectedAssetReference`, `Recovery`, `SecurityAssessment`, `SecurityBoundary`, `SecurityDomain`, `SecurityEntity`, `SecurityEvidence`, `SecurityFinding`, `SecurityIncident`, `SecurityMeasure`, `SecurityPosture`, `SecurityPostureScore`, `SecurityReview`, `SecuritySignal`, `Severity`, `SupplyChainFinding`, `Tactic`, `Threat`, `ThreatActor`, `ThreatEvent`, `Vulnerability`, `VulnerabilityFinding`, `Weakness` ### InfoTechCanon Task Model - ID: `model/task` - Kind: `model` - Canonical path: `models/task/InfoTechCanonTaskModel.md` - Source path: `seeds/InfoTechCanonTaskModel_RC1_seed.md` - Summary: Domain model used by canon profiles and standards: InfoTechCanon Task Model. - Imports and anchors: `kernel/itc-core`, `model/evidence` - Owned concepts: `AcceptanceCriteria`, `Action`, `Actionability`, `ApprovalTask`, `AssignmentReference`, `Backlog`, `Blocker`, `Bug`, `ChangeTask`, `Commitment`, `CompletionEvidence`, `Complexity`, `Deadline`, `DecisionTask`, `DefinitionOfDone`, `DefinitionOfReady`, `Deliverable`, `Dependency`, `DueDate`, `EffortEstimate`, `Epic`, `Experiment`, `Exploration`, `Feature`, `Importance`, `IncidentTask`, `InfoTechCanon Task Model`, `Issue`, `Milestone`, `Move`, `NextAction`, `Option`, `Outcome`, `Priority`, `ProblemTask`, `Reachability`, `Readiness`, `RemediationTask`, `Request`, `ReviewTask`, `Step`, `Story`, `Task`, `TaskEntity`, `Transition`, `Urgency`, `Value`, `WIPLimit`, `WaitingFor`, `WorkItem`, `WorkPackage`, `Workflow`, `WorkflowState` ### Intent Scope Purposes Pattern - ID: `pattern/intent-scope-purposes` - Kind: `pattern` - Canonical path: `patterns/intent-scope-purposes.md` - Source path: `infospace/patterns/intent-scope-purposes.md` - Summary: Reusable canon pattern: Intent Scope Purposes Pattern. - Imports and anchors: `model/governance`, `model/task` - Owned concepts: `Intent Scope Purposes Pattern`, `IntentScopePurposePattern` ### AgenticDrivesFunctional - ID: `practice-pattern/agentic-drives-functional` - Kind: `practice-pattern` - Canonical path: `patterns/AgenticDrivesFunctional.md` - Source path: `patterns/AgenticDrivesFunctional.md` - Summary: Reusable canon PracticePattern: AgenticDrivesFunctional. - Imports and anchors: `model/capability`, `model/governance`, `model/observability`, `model/task`, `scheme/practice-pattern` - Owned concepts: `AgenticDrivesFunctional`, `AgenticFallback`, `DemandSignature`, `FunctionalInterfaceCandidate` ### InterfaceDeprecationStrangler - ID: `practice-pattern/interface-deprecation-strangler` - Kind: `practice-pattern` - Canonical path: `patterns/InterfaceDeprecationStrangler.md` - Source path: `patterns/InterfaceDeprecationStrangler.md` - Summary: Reusable canon PracticePattern: InterfaceDeprecationStrangler. - Imports and anchors: `model/devsecops`, `model/governance`, `model/observability`, `scheme/practice-pattern` - Owned concepts: `InterfaceDeprecationStrangler` ### Intake and Assimilation Practice - ID: `practice/intake-and-assimilation` - Kind: `practice` - Canonical path: `assimilation/intake-and-assimilation-practice.md` - Source path: `assimilation/intake-and-assimilation-practice.md` - Summary: Canon artifact: Intake and Assimilation Practice. - Imports and anchors: `kernel/itc-core` - Owned concepts: `Intake and Assimilation Practice` ### Small SaaS System Profile - ID: `profile/small-saas` - Kind: `profile` - Canonical path: `profiles/small-saas/profile.yaml` - Source path: `infospace/profiles/small-saas/profile.yaml` - Summary: Profile that constrains canon artifacts for a practical implementation slice: Small SaaS System Profile. - Imports and anchors: `kernel/itc-core`, `model/access-control`, `model/data`, `model/devsecops`, `model/governance`, `model/landscape`, `model/network`, `model/observability`, `model/organization`, `model/security`, `model/task`, `standard/caring`, `standard/tagging` - Owned concepts: `Small SaaS System Profile` ### Canon Consumer Alignment Review Kit - ID: `review-kit/alignment` - Kind: `alignment-review-kit` - Canonical path: `agent/review-kit/review-kit.yaml` - Source path: `infospace/agent/review-kit/review-kit.yaml` - Summary: Reusable kit for consumer repository alignment reviews: Canon Consumer Alignment Review Kit. - Imports and anchors: `benchmark/caring/kubernetes-rbac`, `kernel/itc-core`, `model/governance`, `model/purpose-demand-extension`, `model/task`, `standard/caring` - Owned concepts: `Canon Consumer Alignment Review Kit` ### Canon Model And Standard Selection Guide - ID: `review-kit/alignment/model-selection-guide` - Kind: `model-selection-guide` - Canonical path: `agent/review-kit/model-selection-guide.yaml` - Source path: `infospace/agent/review-kit/model-selection-guide.yaml` - Summary: Guide for choosing canon models, standards, profiles, and benchmarks: Canon Model And Standard Selection Guide. - Imports and anchors: `benchmark/caring/kubernetes-rbac`, `model/access-control`, `model/data`, `model/devsecops`, `model/governance`, `model/landscape`, `model/network`, `model/observability`, `model/organization`, `model/purpose-demand-extension`, `model/security`, `model/task`, `profile/small-saas`, `standard/caring`, `standard/tagging` - Owned concepts: `Canon Model And Standard Selection Guide` ### Consumer Alignment Review Schema - ID: `review-kit/alignment/schema` - Kind: `alignment-review-schema` - Canonical path: `schemas/alignment-review.schema.yaml` - Source path: `infospace/schemas/alignment-review.schema.yaml` - Summary: Schema for structured consumer repository alignment reviews: Consumer Alignment Review Schema. - Imports and anchors: `model/governance`, `model/task` - Owned concepts: `Consumer Alignment Review Schema` ### Canon Consumer Alignment Scorecard - ID: `review-kit/alignment/scorecard` - Kind: `alignment-scorecard` - Canonical path: `agent/review-kit/scorecard.yaml` - Source path: `infospace/agent/review-kit/scorecard.yaml` - Summary: Scorecard dimensions for canon alignment reviews: Canon Consumer Alignment Scorecard. - Imports and anchors: `model/governance`, `model/task` - Owned concepts: `Canon Consumer Alignment Scorecard` ### Canon Consumer Alignment Review Workflow - ID: `review-kit/alignment/workflow` - Kind: `alignment-review-workflow` - Canonical path: `agent/review-kit/review-workflow.yaml` - Source path: `infospace/agent/review-kit/review-workflow.yaml` - Summary: Repeatable workflow for canon alignment reviews: Canon Consumer Alignment Review Workflow. - Imports and anchors: `model/governance`, `model/purpose-demand-extension`, `model/task` - Owned concepts: `Canon Consumer Alignment Review Workflow` ### Consumer Alignment Workplan Template - ID: `review-kit/alignment/workplan-template` - Kind: `consumer-workplan-template` - Canonical path: `agent/templates/consumer-alignment-workplan.template.md` - Source path: `infospace/agent/templates/consumer-alignment-workplan.template.md` - Summary: Template for consumer repository alignment workplans: Consumer Alignment Workplan Template. - Imports and anchors: `model/purpose-demand-extension`, `model/task` - Owned concepts: `Consumer Alignment Workplan Template` ### PracticePattern Scheme - ID: `scheme/practice-pattern` - Kind: `practice-pattern-scheme` - Canonical path: `patterns/PracticePatternScheme.md` - Source path: `patterns/PracticePatternScheme.md` - Summary: Contract for canon PracticePattern artifacts: PracticePattern Scheme. - Imports and anchors: `kernel/itc-core` - Owned concepts: `PatternLanguage`, `PracticePattern`, `PracticePattern Scheme` ### Small SaaS Production Capability Requirements - ID: `small-saas/capability-requirements/production` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/capability-requirements.yaml` - Source path: `profiles/small-saas/artifacts/capability-requirements.yaml` - Summary: Example artifact for the small-saas profile: Small SaaS Production Capability Requirements. - Imports and anchors: `model/capability` - Owned concepts: `Small SaaS Production Capability Requirements` ### Namespace Per Tenant Control - ID: `small-saas/control/namespace-per-tenant` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/control.namespace-per-tenant.yaml` - Source path: `profiles/small-saas/artifacts/control.namespace-per-tenant.yaml` - Summary: Example artifact for the small-saas profile: Namespace Per Tenant Control. - Imports and anchors: `model/security`, `standard/caring` - Owned concepts: `Namespace Per Tenant Control` ### Subscription Ledger Dataset - ID: `small-saas/dataset/subscription-ledger` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/dataset.subscription-ledger.yaml` - Source path: `profiles/small-saas/artifacts/dataset.subscription-ledger.yaml` - Summary: Example artifact for the small-saas profile: Subscription Ledger Dataset. - Imports and anchors: `model/data` - Owned concepts: `Subscription Ledger Dataset` ### Production Deployment - ID: `small-saas/deployment/production` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/deployment.production.yaml` - Source path: `profiles/small-saas/artifacts/deployment.production.yaml` - Summary: Example artifact for the small-saas profile: Production Deployment. - Imports and anchors: `model/devsecops`, `model/network` - Owned concepts: `Production Deployment` ### Access Review 2026-05 - ID: `small-saas/evidence/access-review-2026-05` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/evidence.access-review-2026-05.yaml` - Source path: `profiles/small-saas/artifacts/evidence.access-review-2026-05.yaml` - Summary: Example artifact for the small-saas profile: Access Review 2026-05. - Imports and anchors: `model/observability` - Owned concepts: `Access Review 2026-05` ### Cross-Tenant Access Attempt - ID: `small-saas/incident/cross-tenant-access-attempt` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/incident.cross-tenant-access-attempt.yaml` - Source path: `profiles/small-saas/artifacts/incident.cross-tenant-access-attempt.yaml` - Summary: Example artifact for the small-saas profile: Cross-Tenant Access Attempt. - Imports and anchors: `model/security` - Owned concepts: `Cross-Tenant Access Attempt` ### Tenant Isolation Policy - ID: `small-saas/policy/tenant-isolation` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/policy.tenant-isolation.yaml` - Source path: `profiles/small-saas/artifacts/policy.tenant-isolation.yaml` - Summary: Example artifact for the small-saas profile: Tenant Isolation Policy. - Imports and anchors: `model/governance`, `small-saas/control/namespace-per-tenant` - Owned concepts: `Tenant Isolation Policy` ### Billing Portal Service - ID: `small-saas/service/billing-portal` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/service.billing-portal.yaml` - Source path: `profiles/small-saas/artifacts/service.billing-portal.yaml` - Summary: Example artifact for the small-saas profile: Billing Portal Service. - Imports and anchors: `model/landscape` - Owned concepts: `Billing Portal Service` ### Small SaaS Billing System - ID: `small-saas/system/billing-system` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/system.billing-system.yaml` - Source path: `profiles/small-saas/artifacts/system.billing-system.yaml` - Summary: Example artifact for the small-saas profile: Small SaaS Billing System. - Imports and anchors: `model/landscape` - Owned concepts: `Small SaaS Billing System` ### Onboard Tenant - ID: `small-saas/task/onboard-tenant` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/task.onboard-tenant.yaml` - Source path: `profiles/small-saas/artifacts/task.onboard-tenant.yaml` - Summary: Example artifact for the small-saas profile: Onboard Tenant. - Imports and anchors: `model/task` - Owned concepts: `Onboard Tenant` ### Platform Team - ID: `small-saas/team/platform` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/team.platform.yaml` - Source path: `profiles/small-saas/artifacts/team.platform.yaml` - Summary: Example artifact for the small-saas profile: Platform Team. - Imports and anchors: `model/organization` - Owned concepts: `Platform Team` ### Acme Tenant - ID: `small-saas/tenant/acme` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/tenant.acme.yaml` - Source path: `profiles/small-saas/artifacts/tenant.acme.yaml` - Summary: Example artifact for the small-saas profile: Acme Tenant. - Imports and anchors: `model/organization` - Owned concepts: `Acme Tenant` ### Globex Tenant - ID: `small-saas/tenant/globex` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/tenant.globex.yaml` - Source path: `profiles/small-saas/artifacts/tenant.globex.yaml` - Summary: Example artifact for the small-saas profile: Globex Tenant. - Imports and anchors: `model/organization` - Owned concepts: `Globex Tenant` ### Ada Admin - ID: `small-saas/user/ada-admin` - Kind: `profile-artifact` - Canonical path: `profiles/small-saas/artifacts/user.ada-admin.yaml` - Source path: `profiles/small-saas/artifacts/user.ada-admin.yaml` - Summary: Example artifact for the small-saas profile: Ada Admin. - Imports and anchors: `model/access-control`, `model/organization` - Owned concepts: `Ada Admin` ### InfoTechCanon CARING Access Governance Standard - ID: `standard/caring` - Kind: `standard` - Canonical path: `standards/caring/InfoTechCanonCaringAccessGovernanceStandard.md` - Source path: `seeds/InfoTechCanonCaringAccessGovernanceStandard.md` - Summary: Cross-cutting canon standard: InfoTechCanon CARING Access Governance Standard. - Imports and anchors: `kernel/itc-core`, `model/access-control`, `model/data`, `model/devsecops`, `model/evidence`, `model/governance`, `model/network`, `model/observability`, `model/organization`, `model/security`, `model/task`, `standard/tagging` - Owned concepts: `CARINGAccessDescriptor`, `CARINGAnalysisFitnessTest`, `CARINGAnalysisProcedure`, `CARINGCanonicalRole`, `CARINGCapabilityProfile`, `CARINGDeclaredAccessMap`, `CARINGDerivedCapability`, `CARINGEffectiveAccessMap`, `CARINGExposureEvent`, `CARINGExposureMode`, `CARINGInducedAccess`, `CARINGOrganizationRelation`, `CARINGPlane`, `CARINGRedesignProcedure`, `CARINGRestrictionPrecedence`, `Capability Profile`, `Declared Access`, `Derived Capability`, `Effective Access`, `InfoTechCanon CARING Access Governance Standard` ### InfoTechCanon Emission Cadence Standard - ID: `standard/emission-cadence` - Kind: `standard` - Canonical path: `standards/emission-cadence/InfoTechCanonEmissionCadenceStandard.md` - Source path: `infospace/assimilation/emission-cadence/source/EmissionCadenceDeclaration.md` - Summary: Cross-cutting canon standard: InfoTechCanon Emission Cadence Standard. - Imports and anchors: `kernel/itc-core`, `model/governance`, `model/observability` - Owned concepts: `EmissionCadenceDeclaration`, `EmissionCadenceForm`, `ExpectedRateCadence`, `HeartbeatCadence`, `InfoTechCanon Emission Cadence Standard`, `ReconciliationCadence` ### InfoTechCanon Repository Layout Standard - ID: `standard/repository-layout` - Kind: `standard` - Canonical path: `standards/repository-layout/InfoTechCanonRepositoryLayoutStandard.md` - Source path: `infospace/evaluations/repository-layout/source-demand.md` - Summary: Cross-cutting canon standard: InfoTechCanon Repository Layout Standard. - Imports and anchors: `kernel/itc-core`, `model/governance`, `model/information-space`, `model/task` - Owned concepts: `CanonicalRepositoryLayout`, `InfoTechCanon Repository Layout Standard`, `LayoutConformanceLevel`, `RepositoryDocumentationDirectory`, `ScopeIntentOperatingMode` ### InfoTechCanon Tagging Standard - ID: `standard/tagging` - Kind: `standard` - Canonical path: `standards/tagging/InfoTechCanonTaggingStandard.md` - Source path: `seeds/InfoTechCanonTaggingStandard_RC1_seed.md` - Summary: Cross-cutting canon standard: InfoTechCanon Tagging Standard. - Imports and anchors: `kernel/itc-core`, `model/evidence`, `model/task` - Owned concepts: `ControlledTag`, `DeprecatedTag`, `EmergentTag`, `InfoTechCanon Tagging Standard`, `OverTaggedEntity`, `Tag`, `TagAlias`, `TagAssignment`, `TagCategory`, `TagConflict`, `TagDefinition`, `TagDrift`, `TagKey`, `TagMapping`, `TagNamespace`, `TagProfile`, `TagQuery`, `TagRule`, `TagScheme`, `TagSelector`, `TagSet`, `TagValue`, `TagView`, `TaggingEntity`, `UntaggedEntity`