Templates

To bootstrap or synchronize enterprise IT assets into Mopheus, organizations can provide an Excel or CSV asset ledger. When an AI agent reads this ledger, it automatically maps the tabular columns, validates concept schemas, and compiles the records into a fully validated, strongly typed Asset Manifest YAML (AssetManifest), generating both asset instances and topological graph relationships.

To ensure a seamless experience for IT administrators and DBAs, the template breaks down key technical attributes (attributes) and governance labels (labels) into explicit, dedicated columns, avoiding the need to manually concatenate key-value strings.

1. Asset Ledger (Assets Sheet)Copy Anchor Link

This is the primary sheet where core IT entities and their basic relationships are registered.

Column SpecificationsCopy Anchor Link

Sample Data RowsCopy Anchor Link

2. Topology Relations (Relations Sheet - Optional)Copy Anchor Link

For advanced directed topology graphs such as multi-hop routing (routes_to), replication mirroring (replicates_to), or cluster orchestration (manages), additional directed edges can be declared explicitly:

3. Data Ingestion & Usage MethodsCopy Anchor Link

Once the standard Excel / CSV ledger is populated, it can be ingested into Mopheus through two primary methods:

1. Direct AI Agent Ingestion (Recommended): Send the ledger file or paste tabular data directly into a ticket or task conversation. The agent (powered by the built-in mopheus-assets skill) automatically handles header mapping, concept resolution, and schema validation, then generates and applies the declarative manifest.
2. Declarative Manifest CLI (mop asset apply): Engineers can compile the ledger into an AssetManifest YAML and apply it using mop asset apply -f <manifest.yaml>. Keep SSH accounts in a separate mode 0600 credential file and pass it with --credentials-file; never put SSH secrets in asset attributes. For detailed schema constraints and topological relationship axioms, refer to Ontology & Schema Reference.

4. Agent Generated YAML OutputCopy Anchor Link

When an agent processes this tabular ledger, it automatically compiles the columns into an AssetManifest:

version: v1
kind: AssetManifest
metadata:
  workspace: ecommerce-prod
  environment: prod
assets:
  - id: svc:order-gateway
    concept: Service
    name: Order Processing Gateway
    aliases:
      - order-gw
      - order-api
    status: active
    environment: prod
    attributes:
      ip: 10.10.1.11
      port: 8080
      engine: spring-boot
      role: gateway
      version: 2.4.0
      zone: zone-a
      codebase_repo: git@github.com:mall/order-gateway.git
    labels:
      owner_team: order-dev
      tier: P0
      oncall: order-lead
      department: E-Commerce Engineering

  - id: db:settle-oracle-rac
    concept: Database
    name: Settlement Oracle 19c RAC
    aliases:
      - settle-db
      - orcl-rac
    status: active
    environment: prod
    attributes:
      ip: 10.10.2.100
      port: 1521
      engine: oracle
      db_mode: rac
      version: 19.21.0.0
      zone: zone-a
      credential_ref: vault://db/oracle-rac
    labels:
      owner_team: billing-dba
      tier: P0
      oncall: dba-lead
      department: Finance Data Team

relations:
  - subject: app:mall-core
    predicate: contains
    object: svc:order-gateway
  - subject: svc:order-gateway
    predicate: runs_on
    object: host:k8s-worker-01
  - subject: svc:order-gateway
    predicate: depends_on
    object: db:settle-oracle-rac
  - subject: svc:order-gateway
    predicate: depends_on
    object: mq:event-kafka