Projects

Everything in Deerlight belongs to a project: documents, skills, and knowledge.

Hierarchy

Projects can contain subprojects at any depth. This is more than folder-style organization: conventions in a parent project remain available to its descendants.

For example:

Team conventions
├── Customer portal
│   ├── Frontend
│   └── Backend
└── Data platform

Put a shared commit-message convention under Team conventions, and an AI assistant working in Frontend can still read it. You do not need to copy it into every child.

Stages

A project can be incubating, validating, implementing, operating, accepting, paused, or archived.

Stages are a human judgment that helps you scan the project list. Only you advance a project stage. An AI assistant does not make that decision for you.

What a project contains

Open a project to see:

• Activity — what changed recently and who changed it;
• Documents — durable material owned by the project;
• Knowledge — compact entries that have been approved;
• Skills — reusable ways of working scoped to the project;
• Subprojects — the projects directly below it.

Bring in existing material

A new project starts empty. You can populate it in two ways:

Import previous sessions — conversations with AI assistants often contain useful decisions and conventions. Import them, let an assistant organize candidate knowledge, and approve what belongs.

Import a repository — bring in selected README files, designs, and runbooks from a code repository.

Imported knowledge enters Review before it becomes official.

Delete a project

Deleting a project removes all of its content and cannot be undone. Deerlight refuses to delete a project that still has children; deal with those children first so one mistake cannot erase a whole tree.