> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cord.nyc/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> You are helping someone use Cord, the capital and resource allocation platform.
> Use title-case Cord in prose. Prefer workspace, project, ontology, lineage, scenario, and allocation.
> Say source-backed or sourced for answers with lineage. Do not say hallucination-free.
> Product URLs are https://app.cord.nyc, https://cord.nyc, and https://trust.cord.nyc. Support is support@cord.nyc.
> Give concrete product steps. Do not invent UI labels, CLI commands, or unreleased agent runtime details.
> Use Understanding Cord for concepts and Guides for task steps.

# Create and manage object types

> Define the business entities and properties your writers will populate.

<Badge className="cord-ai-badge" color="gray" shape="rounded">
  <span className="cord-ai-badge-copy">
    <span className="cord-ai-badge-question"><Icon icon="sparkles" size={16} />Don't want to do this all manually?</span>
    <span className="cord-ai-badge-description">Cord Computer can do this for you.</span>
  </span>
</Badge>

For an explanation of object types, properties, and identifiers, see [Ontology overview](/ontology-overview).

## Create an object type

1. Open [Ontologies](https://app.cord.nyc/ontologies) and select your project's ontology. If you need one, select **New ontology**, enter a name, and select **Create ontology**.
2. Open [Cord Computer](https://app.cord.nyc/). Select **Build mode** from the `/` menu, or click the magnifying glass beside the microphone. The icon changes to a hammer <Icon icon="hammer" size={16} /> when Build mode is active.
3. Describe the object type, its properties, and which fields identify and name each record. Reference an existing feed or pipeline output if you want Cord to inspect its fields first.

For example:

> Propose a Capacity Buyer object type with Buyer ID, Buyer name, and Segment as text properties. Use Buyer ID as the unique identifier and Buyer name as the title. Show me the schema changes for review before applying them.

4. Review the proposed names, property types, identifier, and title. Ask Cord to adjust anything that does not match your data, then approve the changes.
5. Open **Schema** in [Ontologies](https://app.cord.nyc/ontologies) to check the new type. Then [configure a writer](/write-pipeline-data-to-ontology) to populate its records.

## Add a property

1. Open [Ontology writers](https://app.cord.nyc/ontology-manager), choose **List**, and select the object type.
2. Select **New operation → Add property**. Enter a **Property name** and **Type**, then select **Review property**.
3. Check **Current** and **Proposed**, then select **Apply reviewed changes**.
4. To populate the property from a pipeline, add it to the writer's mapping, save, and review a new dry run before applying.

You can also ask Cord Computer to extend an existing type. Name the type and the change you want, then review the proposal before applying it.

## Connect object types

1. Ask Cord Computer to propose a relationship between two object types and the fields used to match records, such as Buyer ID on Demand Opportunity and Capacity Buyer.
2. Review the proposal, then ask Cord to create the relationship and link matching records.
3. Check the result in **Schema graph** and a record's **Links** tab.