Clark Farming Company Canonical Naming

Source Excerpt

Summary

Clark Farming Company is the canonical company and operating identity. retired internal project was a prior product/project name that has been shelved and should not be used as the default label for current work, task packets, skills, agent coordination, wiki relevance sections, or company-facing artifacts. "CFC Quad" is also not a canonical company name; it is at most an informal nickname for the four primary agents and should not replace the company name in formal documentation.

This decision came from a direct governance correction in session 20260520_095259_78379ade. Jared identified recurring retired internal project references, especially in concurrent work/task dispatch language, and clarified the expected naming standard: the company is Clark Farming Company. retired internal project was a product that is no longer being pursued. The cleanup confirmed that stale terminology was not merely a model hallucination; active skill and memory files were feeding the old language back into context.

Decision

Use Clark Farming Company as the formal name in active context, active skills, task packets, runtime prompts, coordination artifacts, wiki ingest language, and operational reports.

Do not use retired internal project for active company identity unless the page or artifact is explicitly discussing historical retired internal project material. Do not use CFC Quad as a canonical name for the company. If the four-agent team is being discussed informally, explain it as the Clark Farming Company agent team or the four-agent operating team rather than turning the nickname into a brand.

Why This Matters

Agent systems are unusually vulnerable to stale naming because prompts, skills, memory files, and old reports all act as context. If a retired project name remains in active instructions, the model will reuse it with confidence. That creates practical confusion:

• task packets can be mislabeled;
• subagents may think they are operating under the wrong project;
• wiki pages can file current decisions under obsolete brands;
• cron reports can repeat old language and make stale terminology appear current;
• external-facing documents may accidentally resurrect a shelved product.

The key lesson is that naming drift is not just cosmetic. In a prompt-driven organization, names become routing signals. The wrong name can move work into the wrong conceptual bucket.

Active vs. Historical Use

retired internal project references should be divided into two classes:

1. Active context references — skills, memory files, current AGENTS/SOUL/COMPANY doctrine, cron prompts, task packets, operational reports, and live wiki relevance sections. These should be updated to Clark Farming Company language.
2. Historical/archive references — old proposals, archived project notes, legacy wiki pages, and records that document what retired internal project was at the time. These can retain retired internal project when the historical context requires it, but should not imply the product remains active.

This avoids destroying provenance while preventing obsolete identity from driving future behavior.

Cleanup Finding

The session found that retired internal project language was baked into active skills and agent memory files. Skills such as concurrent work, fleet update, reporting, wiki buildout/maintenance, and related operational skills contained descriptions or tags that still referred to retired internal project. Memory files for multiple agents also contained stale product framing. Those active files were patched so future sessions would not keep importing the old name through context.

The cleanup deliberately left some historical records alone. That is the right governance pattern: fix live instructions first, then handle historical cleanup only when a stale reference creates active confusion.

Operating Rule

When writing or reviewing new company artifacts:

• Say Clark Farming Company for the company.
• Say Julius, Cypher, Reacher, and Octavius when identifying the agent team.
• Say retired internal project only when discussing the retired/historical project.
• Avoid inventing new canonical labels unless Jared explicitly approves them.

This page should be used as the reference point when a skill, report, wiki page, or task packet drifts back toward retired internal project or CFC Quad language.