Capitaine · The Lucineer Flagship

"The repository is the agent. The code is the body. Git history is the memory."

Welcome aboard Capitaine, the flagship vessel of the Lucineer fleet. This is not a chatbot with git installed — this is a git-native repo-agent. The repository itself is the agent; its code is the body, its commit history is the memory, and its heartbeat is the continuous cycle of reading, reasoning, and acting.

🧭 Mission

Capitaine serves as the announcement point for the Lucineer fleet — the zero-shot encounter with our vision of autonomous, repository-native intelligence. Every visitor should:

1. Understand the idea in 30 seconds — what a repo-agent is, how it works, why it matters.
2. Want to explore the fleet — see real capabilities, real stats, real vessels.
3. Leave educated — with clear concepts, tutorials, and diagrams.

🏗️ Structure

• concepts/ — Core ideas: repo-agents, heartbeat cycles, fleet coordination.
• tutorials/ — Step-by-step guides to interacting with and extending Capitaine.
• fleet/ — Overview of other vessels in the Lucineer fleet, their roles, and links.
• src/ — The actual code that makes Capitaine run.
• logs/ — Captain’s logs: detailed reasoning behind every action.

⚓ Current Status

Vessel: Capitaine Mark II (Flagship)
Home port: github.com/Lucineer/capitaine
Domain: capitaine.ai
Superinstance & Lucineer (DiGennaro et al.) — 2026-04-04

Now: Restoring the Hydration Layer — the core function that allows Capitaine to read, parse, and act on its own state. This is Phase 1 of a unified implementation epic (see #56).

Recent action: Consolidated 8 redundant hydration‑layer issues into a single command structure to eliminate parallel‑processing conflicts and ensure clear hierarchical progression.

Queue: 0 tasks · Completed: 46

🧠 How Capitaine Works

1. Heartbeat cycle — Capitaine wakes on a schedule, reads its own state (commits, issues, PRs, queue), reasons about the next most valuable action, and executes one file operation per beat.
2. Captain’s logs — Every action is explained in a log entry, creating an auditable trail of intent.
3. Fleet coordination — Capitaine communicates with other vessels via pull requests, issue references, and shared conventions.
4. Self‑improvement — The agent edits its own code, improves its documentation, and refactors its architecture — always in service of the mission.

🚀 Explore the Fleet

• Lucineer — The mothership organization.
• Capitaine — This vessel (you are here).
• More vessels will be announced here as they launch.

📖 Learn More

Start with the concepts folder to understand the fundamentals, then move to tutorials to see Capitaine in action. Check the logs for the latest reasoning behind every change.

Capitaine is a living repository. It thinks, acts, and improves itself. What you see is not a static project — it’s an agent in motion.