A registry of 111 research contours: 82 subject models, 18 landscapes, 10 shared contracts and the composition foundation. Each one declares its boundary, questions, invariants and an acceptance scenario.
Hand this text to your AI agent. Company data and access rules stay in your Dimension.
The selections verify package presence and integrity. Compatibility of specific profiles and relations with local master systems are checked at installation. HR, contracts and the legal entity are added only when needed.
Queued means an assignment is prepared. Researching means a pass has started. Completion and publication are confirmed separately.
EM-ORG-01Subject modelBusiness identity of an organization and an explicitly justified group perimeter. Legal personality and ownership shares belong to neighboring models.
Queued for research
EM-ORG-02Subject modelThe legal subject, registry records, branches and legal succession. A registry record has its own identity and a verifiable basis.
Queued for research
EM-ORG-03Subject modelParticipation, votes, control, governing bodies, mandates and decisions. Investment value and financial postings remain in the financial models.
Queued for research
EM-ORG-04Subject modelA unit as a stable unit of responsibility. The org chart is a separate landscape; a team may be an independent collective.
Queued for research
EM-ORG-05Subject modelTeams, temporary collectives and communities of practice; time-bounded membership and working agreements. Membership must not be conflated with employment or authority.
Queued for research
EM-ORG-06Subject modelStaff positions and functional roles; responsibility, decision rights and RACI. The assignment of a person is held by the work relationship, and grade definitions are kept separately.
Queued for research
EM-ORG-07Subject modelThe contextual relationship of a person or organization to a decision subject, with interests, influence and mode of engagement.
Queued for research
EM-PEO-01Subject modelThe minimal identity of a natural person and permitted contacts. HR, customer and technical roles reference the person under a disclosure agreement.
Queued for research
EM-PEO-02Subject modelEmployment, contractor and agency relationships, the employee profile at the employer, assignments and entry/exit events. The onboarding process references process and access as links.
Queued for research
EM-PEO-03Subject modelSkill definition, proficiency scale, assessment, qualification credential and validity period. The professional role uses these definitions.
Queued for research
EM-PEO-04Subject modelThe approved need, the vacancy, the candidacy, selection stages and the offer. Person, position, budget and the employment relationship have external owners.
Queued for research
EM-PEO-05Subject modelTraining programs and participation, development plans, career paths and succession plans. The fact of training and a qualification are distinct.
Queued for research
EM-PEO-06Subject modelThe review cycle, criteria, observations, feedback, achievements, disputes and calibration decisions. Assessments must not become permanent properties of a person.
Partially published; research continues
EM-PEO-07Subject modelWork calendars, absence and available capacity; actual time records and their approval. Allocation of capacity across work items is a separate model.
Queued for research
EM-PEO-08Subject modelVersioned level systems, expectation profiles per role, level assignment and calibration. Level of responsibility, qualification and compensation are related but distinct.
Queued for research
EM-PEO-09Subject modelCompensation ranges, individual assignments and benefit plans. Payroll calculation and mandatory rules are attached via jurisdictional profiles.
Queued for research
EM-STR-01Subject modelChoice of markets, value proposition, the mechanism of producing outcomes, strategic hypotheses and the value stream. Projects do not substitute for strategy.
Queued for research
EM-STR-02Subject modelGoals, measurable target states, expected and realized benefits. The method of valuing benefit and harm is set by an explicit profile.
Queued for research
EM-STR-03Subject modelThe enterprise's ability to achieve a defined class of outcomes independently of the current structure and means of implementation.
Queued for research
EM-STR-04Subject modelA proposed change, the problem, alternatives, the business case, assumptions and the decisions to move to execution.
Queued for research
EM-WRK-01Subject modelTasks and typed work items, backlog, iterations, workflow, estimates and completion criteria. Jira types are adapters, not a universal ontology.
Queued for research
EM-WRK-02Subject modelThe business project, charter, plan, milestones, deliverables, acceptance and baseline changes. The product and the tracking system have separate identities.
Queued for research
EM-WRK-03Subject modelCoordinated projects and other work pursued for joint benefits, with management of the transition and the sustainability of the effect.
Queued for research
EM-WRK-04Subject modelSelection and balancing of initiatives, projects, programs and product investments within the strategy and its constraints.
Queued for research
EM-WRK-05Subject modelDemand, available capacity and assignments of human and other resources to work. Human engagement, money and compute have different units.
Queued for research
EM-WRK-06Subject modelTyped cross-object dependencies, prerequisites and constraints with scope and evidence. Does not imply automatic causality.
Queued for research
EM-PRD-01Subject modelThe product as a managed outcome for a consumer, offering variants, prices and development intents. The physical instance, the software and the actual delivery have separate boundaries.
Queued for research
EM-PRD-02Subject modelThe service, the expected outcome, the terms of provision and consumption. The running service instance and the service level agreement are delegated.
Queued for research
EM-PRD-03Subject modelRequirements, constraints, acceptance criteria and traceability to the solution. An implementation task references a requirement.
Queued for research
EM-PRD-04Subject modelResearch question, hypothesis, experiment design, run and interpretation of the result. AI training and evaluation use specialized child models.
Queued for research
EM-PRD-05Subject modelProtected object, application, registration, ownership and licensed use. The brand as a business association is separated from the trademark.
Queued for research
EM-COM-01Subject modelCounterparty roles, relationships, contact assignments and segmentation. The person or organization itself is reused by identity.
Queued for research
EM-COM-02Subject modelLead, opportunity, quote, campaign and attribution. Counterparty relationships and concluded contracts have their own owners.
Queued for research
EM-COM-03Subject modelOrder and lines, subscription, changes and the consumer's entitlement. Invoice, payment, software license and usage are kept separate.
Queued for research
EM-COM-04Subject modelExternal inquiry, service request, communications and resolution. An incident is a separate fact of disruption linked to many inquiries.
Queued for research
EM-LEG-01Subject modelAgreement of the parties, versions, terms, obligations, confirmation of performance and SLA/OLA. Operational SLO and metrics are moved to their own models.
Queued for research
EM-LEG-02Subject modelVersions of external requirements, territories, addressees and justified applicability assessments. The model does not make a legal decision in place of the responsible specialist.
Queued for research
EM-LEG-03Subject modelInternal rules, adoption, applicability, exceptions and acknowledgment. The result of an enforcement check belongs to the control model.
Queued for research
EM-LEG-04Subject modelA permit from an authorized body, subject, territory, conditions and term. Commercial entitlement and IP grant are mapped but not merged.
Queued for research
EM-LEG-05Subject modelCase, parties to the proceedings, claims, events and decisions. Contract, evidence and financial reserve remain references.
Queued for research
EM-LEG-06Subject modelProcessing purpose, data categories, participant roles, legal basis, retention periods and data subject requests. Jurisdictional rules are defined by verified profiles.
Queued for research
EM-FIN-01Subject modelFunds plan, scenarios, limits, cost centers and responsibility. An organizational unit is not required to coincide with a financial center.
Queued for research
EM-FIN-02Subject modelLedger accounts, journals, entries and settlement events. A bank account and a ledger account differ; the model integrates the ERP, it does not replace its period closing.
Queued for research
EM-FIN-03Subject modelSettlement document, lines, due dates, payments and their allocation. The names invoice, bill and tax invoice require local profiles.
Queued for research
EM-FIN-04Subject modelFinancial report, consolidation perimeter, transformation rules and elimination of intragroup transactions. Common definitions of the report and the run are reused.
Queued for research
EM-FIN-05Subject modelExpenses and measured consumption, allocation, unit economics and FinOps. Price, cost and accounting recognition are not identical.
Queued for research
EM-FIN-06Subject modelInvestment stake, instrument, deal, valuation and assumptions. Voting and corporate control belong to the corporate model.
Queued for research
EM-FIN-07Subject modelJurisdictional tax profile, period, computation, filing and settlements with the authority. Specific rates and rules are researched against current primary sources.
Queued for research
EM-OPS-01Subject modelProcess definition, steps, procedure and a specific execution instance. A methodology sets the rules of work, not a new process instance.
Queued for research
EM-OPS-02Subject modelNeed, purchase request, procedure, bids, evaluation and decision. The order and the contract use the commercial models.
Queued for research
EM-OPS-03Subject modelTracked asset instance, ownership, operation, maintenance, inspections and calibration. A configuration item is linked to the asset but is not identical to it.
Queued for research
EM-OPS-04Subject modelProduct class, SKU, engineering revision, EBOM/MBOM, components and allowed substitutions. The software image and the serial instance have separate identities.
Queued for research
EM-OPS-05Subject modelBatches, serialized units, stock levels, transformations, movements and shipments. The balance is derived from events with explicit adjustments.
Queued for research
EM-TEC-01Subject modelSoftware identity, architecture, components, repositories, builds, releases and delivered artifacts. Research delegation to specialized models within the full AISMM product context.
Queued for research
EM-TEC-02Subject modelA system used by the organization, business application, module and purpose. The vendor's product, the purchased license and the running instance differ.
Queued for research
EM-TEC-03Subject modelInteraction contract, interface version, integration link, endpoint binding and exchange. The data schema and the transport are not equal to the business agreement.
Queued for research
EM-TEC-04Subject modelDeployed instance, environment, infrastructure resource, configuration item and technical topology. VM image, physical asset and product are kept separate.
Queued for research
EM-TEC-05Subject modelService disruption, cause investigation, impact, response and recovery. Incident, problem, security event, defect and task play different roles.
Queued for research
EM-TEC-06Subject modelSLI specification, SLO target, evaluation window, error budget and reaction rules. Metric definitions and observations are reused from the analytics foundation.
Queued for research
EM-TEC-07Subject modelVulnerability description, affectedness assessment, priority and remediation confirmation. A discovered weakness is not identical to its exploitation.
Queued for research
EM-TEC-08Subject modelTest specification, run, result, evidence and defect as a nonconformity claim. The remediation work item has an independent lifecycle.
Queued for research
EM-TEC-09Subject modelTechnology catalog, adoption stages, architecture standard, adoption and conformance assessment. ADR reuses the decision model.
Queued for research
EM-TEC-10Subject modelChange request, approval decision, window, execution, rollback and on-call schedule. Person assignment and release are delegated to their own models.
Queued for research
EM-DAT-01Subject modelDataset, versions, distribution, schema, contract for quality and permitted use. The catalog record is not the dataset itself.
Queued for research
EM-DAT-02Subject modelA managed data offering with consumers, a quality promise and interfaces. The dataset itself and the pipeline are not duplicated.
Queued for research
EM-DAT-03Subject modelTransformation definition, job, run, inputs and outputs, lineage at the dataset and field level. High-volume logs remain in external storage.
Queued for research
EM-DAT-04Subject modelQuality rule, measurement, violation, coverage and remediation plan. Source completeness, field fill rate and truth of facts are different indicators.
Queued for research
EM-DAT-05Subject modelDefinition of the measured quantity, unit, breakdowns, calculation, observation and target value. The formula and the measured result have different versions.
Queued for research
EM-DAT-06Subject modelReport specification, parameters, run, publication and artifact. A dashboard is a set of permitted projections or a view of an explicitly modeled aggregate.
Queued for research
EM-DAT-07Subject modelAnalysis question, population, method, result, limitations and recommendation. A report shows results but does not replace the justification of the conclusion.
Queued for research
EM-AI-01Subject modelAI system in its context of use, agent configuration, tools, execution and endpoint. The subject of authority remains a defined operator, not automatically a new person.
Queued for research
EM-AI-02Subject modelModel definition, artifact versions, training/fine-tune run, configuration, compute and data provenance. Weights are stored outside the public catalog.
Queued for research
EM-AI-03Subject modelEvaluation plan, benchmark, run, results, risk assessment and decision on permissible use. Metric, dataset and evidence are reused.
Queued for research
EM-KNW-01Subject modelInformation object, revisions, publications, concepts and definitions. The file is a carrier, while claims and decisions have their own references.
Queued for research
EM-KNW-02Subject modelClaim, evidence, argument, alternatives and decision, including ADR. Evidence can support multiple assessments without copying.
Queued for research
EM-KNW-03Subject modelMeeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Queued for research
EM-RSK-01Subject modelRisk in context, assessment, mitigation measure, control and execution. Requirement, policy and evidence are imported by reference.
Queued for research
EM-RSK-02Subject modelReview plan, criteria, sample, evidence, finding and corrective action. An audit opinion has a scope and limitations.
Queued for research
EM-RSK-03Subject modelAccount, access role, permission, delegation, access review and key metadata. Credential values are not part of the registry.
Queued for research
EM-RSK-04Subject modelCriticality, continuity plan, backup policy, recovery objective, exercise and recovery evidence. A successful backup does not confirm recoverability.
Queued for research
EM-FAC-01Subject modelGeographic location, site, building, room and workplace with assignment and accessibility. Leases, assets and people assignments are linked externally.
Queued for research
EM-FAC-02Subject modelInventory boundary, activity, impact factor, calculation and disclosure. Methodologies and assumptions are versioned; financial costs do not substitute for impact.
Queued for research
EM-LND-01LandscapeA versioned graph of organizational units, positions, teams and assignments along independent axes.
Queued for research
EM-LND-02LandscapeAn overview of the group's business perimeters, legal entities, control and mandates without moving it into a mandatory Universe.
Queued for research
EM-LND-03LandscapeComposition of people, relationships, qualifications, assignments and availability within a permitted management context.
Queued for research
EM-LND-04LandscapeLinks between intents, goals, capabilities, initiatives, benefits and Dimensions.
Queued for research
EM-LND-05LandscapeComposition of management initiatives, dependencies, resources and expected benefits through self-contained objects.
Queued for research
EM-LND-06LandscapeComposition, interactions, ownership, criticality and evolution of software across products. PLMM is a candidate; its status and version require a separate decision.
Queued for research
EM-LND-07LandscapeManagement overview of offerings, lifecycles, consumers and economics.
Queued for research
EM-LND-08LandscapeRelationships with the market, counterparties, opportunities, orders and channels.
Queued for research
EM-LND-09LandscapeA map of parties, agreements, obligations, deadlines and fulfillment dependencies.
Queued for research
EM-LND-10LandscapePlans, actuals, responsibility centers and consolidation perimeters with matching rules.
Queued for research
EM-LND-11LandscapeFlows of sourcing, transformations, inventory and deliveries with item-level traceability.
Queued for research
EM-LND-12LandscapeLinks between consumer services, applications, instances, infrastructure and operational responsibility.
Queued for research
EM-LND-13LandscapeData provenance, indicator semantics, report releases and analytical conclusions.
Queued for research
EM-LND-14LandscapeLinks between research, models, datasets, runs, evaluations, systems and consumed resources.
Queued for research
EM-LND-15LandscapeLinks between requirements, risks, controls, assessments and findings over an explicit perimeter.
Queued for research
EM-LND-16LandscapeSemantic links between documents, concepts, assertions, evidence and decisions.
Queued for research
EM-LND-17LandscapePlacement, ownership, usage and maintenance of assets in space.
Queued for research
EM-LND-18LandscapeA composition of selected domain landscapes for specific management questions. Not a universal copy of all enterprise data and not a kernel.
Queued for research
EM-XCT-01Shared contractA shared contract for identifiers, aliases, same-as claims, merge/split and reversible mappings.
Partially published; research continues
EM-XCT-02Shared contractA contract for semantic owner, steward, master system and change rights at the fact-type level.
Partially published; research continues
EM-XCT-03Shared contractA common form for source, derivation, confirmation level, uncertainty and knowledge correction.
Partially published; research continues
EM-XCT-04Shared contractA shared contract for valid time, recorded time, revisions, states and schema versions without a universal domain lifecycle.
Partially published; research continues
EM-XCT-05Shared contractA shared contract for sensitivity, purpose, retention and permitted Projection fields. Specific IAM grants belong to the access model.
Partially published; research continues
EM-XCT-06Shared contractReusable types for quantities, currencies, ranges, dates, calendars and localized labels.
Partially published; research continues
EM-XCT-07Shared contractThe form of a permitted action, its preconditions, effect, confirmation and idempotency.
Partially published; research continues
EM-XCT-08Shared contractDescription of a master system, physical binding, extraction, snapshot, watermark and conflict. Local addresses and credentials are not published in the shared library.
Partially published; research continues
EM-XCT-09Shared contractA contract for concept schemes, codes, versions, profiles and exact/broad/narrow/related mapping relations.
Partially published; research continues
EM-XCT-10Shared contractResearch into the publication contract: manifest, role, schema, semantic version, digest, fingerprint, dependencies, holds and withdrawal.
Being researched
EM-KRN-01Composition foundationInvestigate the boundary between the Vercy kernel, the declared ELMM composition kernel and the Enterprise Landscape. ELMM is absent from the verified runtime: this is an assignment, not a finished package.
Partially published; research continues
Claude and Grok research each boundary and its sources independently. Their findings are compared, disagreements are preserved, then schema, semantics, dependencies and scenarios are checked. A finished result is published immediately with an honest maturity status. The registry does not claim that all 111 studies are already done.