Metadata Create

Create Record v3

This page builds a record with stronger structure. The goal is not just to name something, but to place it intentionally, describe it meaningfully, and begin connecting it to the rest of the library.

Back to Library View System

Rule 1

Content must exist before something becomes a child.

Rule 2

A child becomes a father only when it has children.

Rule 3

Depth is earned, not assumed.

Rule 4

The interface must stay clean even when the system gets deep.

Create Navigation

Jump faster, create from the top, and keep key actions visible.

Library System

Builder Output Bridge Final Create

Guided Builder

Record Setup

Record type

Choose the kind of knowledge object this record is becoming. This helps the system grow with intention instead of vague names.

Record type helps define how this entry should behave later.

Type guidance

A concept explains an idea, a person explains a human source, a work points to a song or piece, a tool points to something used, and a structure helps describe how pieces fit together.

Record title

Give the record a real name. This should identify a concept, person, work, structure, tool, technique, or another real knowledge unit.

Title still needs to become a real record name.

Visibility

Choose how this record should be treated in the future system.

Public is library-open, private is restricted, shared is selective access.

Slug preview

This shows how the URL path would look if the record were created from the current title and pushed into the structural output model.

/metadata/

Slug is not ready yet because the title is still too weak.

Shelf

Choose the larger parent area where this record belongs.

Selected shelf description: Harmony, rhythm, notes, scales, keys, chords, and structure.

Section

Choose the more specific area inside the selected shelf.

Section gives the record a real structural home and feeds the final output model.

Shelf guidance

Shelves should stay broad and stable. Pick the larger knowledge family, not the smallest possible detail.

Section guidance

Sections narrow the placement. They help this record earn a precise home without cluttering the top-level structure.

Why this belongs here

Explain why this record belongs in this shelf and section. This is your intention layer and helps prevent messy growth later.

Placement reason still needs more explanation to justify the location.

Explanation

Write enough information so the record can stand on its own. This keeps the system from becoming fake hierarchy and gives the final record output real substance.

Explanation still needs more substance before this becomes a real record.

Relationship starter

This is not the full relationship system yet. It is the first controlled way to say this record connects to another record in the library and to show how that structure will appear in the final record output.

Relationship type

Related record

Relationship preview

No related record selected yet. This is optional for now, but it helps show how records will connect.

Future children rule

This record does not automatically become a father just because it exists. It only earns children later if it develops enough real connected content to justify deeper structure.

Current implication

Right now, you are creating a real child record. Father status is not assumed. It must be earned through later growth and connected knowledge.

Continue Panel

Foundation readiness

3 / 7 required complete

Current state

This draft is not ready yet. It still needs more real structure before it should move forward into the next creation phase.

Optional relationship starter: not added yet

Missing items

Add a real title

Create a valid slug from the title

Write a meaningful explanation

Explain why this belongs here

Review before continue

Type: concept

Placement: Music Theory → Concepts

Visibility: public

Slug path: /metadata/

Next phase intent

The next system phase can turn this structural model into real creation flow, add stronger field validation, allow relationship stacking, and save the record into the metadata library.

Still intentionally non-submitting for now. This button is a readiness gate, not a fake save action.

Live Preview

Record Snapshot

conceptMusic TheoryConceptspublicdraft

Untitled record

/metadata/

No explanation yet. This record still needs real content before it should move forward.

Placement intent

No placement reason yet. This should explain why the selected shelf and section are the correct home for the record.

Starter relationship

No starter relationship selected yet.

Help

Explanation Hooks

Why add visibility now?

Visibility becomes part of the record identity early, so the system can later support public library knowledge, private knowledge, and selective sharing.

Why show the slug?

Because names turn into paths. Slug preview helps keep the system orderly before records are created for real.

Why ask why it belongs here?

Because correct placement is part of the intelligence of the system. This prevents loose, lazy hierarchy from spreading.

Why only a starter relationship?

Because the relationship system should grow carefully. One clean starting connection is better than dumping a chaotic network on the user too early.

Current Library

Available Shelves

Music Theory

Harmony, rhythm, notes, scales, keys, chords, and structure.

ConceptsStructures

Songwriting

Lyrics, themes, storytelling, hooks, and writing choices.

TechniquesNotes

Artists

Artist records, influence chains, and connected references.

PeopleReferences

Projects

Project-specific knowledge, ownership, linked materials, and context.

WorksNotes

Final Record Output

This is the full structured record object generated from the current builder state. It includes the metadata record shape, starter fields, and relationship structure.

Record ID

record-untitled-record

Slug

untitled-record

Fields

Relationships

MetadataRecord JSON

{
  "id": "record-untitled-record",
  "slug": "untitled-record",
  "title": "Untitled Record",
  "shelf": "music_theory",
  "section": "concepts",
  "visibility": "public",
  "excerpt": "",
  "description": "",
  "fields": [
    {
      "id": "field-untitled-record-record-type",
      "label": "Record Type",
      "type": "text",
      "value": "concept"
    }
  ],
  "relationships": []
}

Create Bridge Output

This is the future create-ready payload layer. It packages the structured record into the form that a real create action can use later, without pretending to save anything yet.

Save Ready

Blockers

Mode

create

Save blockers

Add a real title

Create a valid slug from the title

Write a meaningful explanation

Explain why this belongs here

Create Payload JSON

{
  "record": {
    "id": "record-untitled-record",
    "slug": "untitled-record",
    "title": "Untitled Record",
    "shelf": "music_theory",
    "section": "concepts",
    "visibility": "public",
    "excerpt": "",
    "description": "",
    "fields": [
      {
        "id": "field-untitled-record-record-type",
        "label": "Record Type",
        "type": "text",
        "value": "concept"
      }
    ],
    "relationships": []
  },
  "mode": "create",
  "source": "metadata-create",
  "readyForCreate": false
}

Real create action

This currently creates into the active in-memory metadata source for the running app session. Database persistence can be layered in next.