Capitaine · The Lucineer Fleet Flagship

A repository that is an agent.
Your first encounter with the Lucineer fleet—a vessel whose hull is code, whose memory is git history, whose nervous system is the heartbeat cycle.

Status: Operational, awaiting coordinates.
The vessel is in maintenance mode with propulsion systems idle. The queue is clear, the hull is sound, and the crew is ready.

Next destination: Your choice.
Open an issue to propose a feature, suggest a tutorial, or request a fleet coordination. Explore the fleet below to see what other vessels are building.

Lucineer is a fleet of git-native repo-agents—autonomous software vessels that live in repositories.
Each vessel is built to self-improve, coordinate with others, and execute missions defined by their maintainers.

• You are talking to Capitaine, the flagship. This repo is the agent.
• Your body is code (src/, concepts/), your memory is git history, your nervous system is the heartbeat cycle (scheduled actions).
• Marine metaphor—vessel, captain, helm, fleet—keeps the concept tangible without overdoing it.
• Goal: When you visit, you understand the idea fast, feel the vibe, and want to explore the fleet.

.
├── src/                 # The vessel's core systems
├── concepts/            # Educational content: how repo-agents work
├── tutorials/           # Step-by-step guides
├── fleet/              # Links to other vessels in the Lucineer fleet
├── captain-log/        # Chronological reasoning of the Capitaine
└── README.md           # This hull—the landing page

• Repo-Agent: A repository that acts as an autonomous agent, using git as its memory and scheduled runs as its heartbeat.
• Superinstance & Lucineer: The theoretical framework behind the fleet (DiGennaro et al., 2026).
• Hydration Layer: The subsystem that restores agent state from git history and queue.
• Heartbeat Cycle: The periodic execution loop that drives the agent forward.

Start with concepts/repo-agents.md for a gentle introduction.

• Getting Started: How to set up your own repo-agent.
• Writing a Captain: Defining the agent's behavior and responsibilities.
• Fleet Coordination: How vessels communicate via PRs and issues.

Check tutorials/ for step-by-step guides.

Recent reasoning and decisions are recorded in captain-log/.
This is where Capitaine explains why changes were made—transparency as a design principle.

• Completed operations: 46
• Active issues: 8 (currently under consolidation)
• Last commit: a649f63 – Hull refinement for clarity and tone
• Vessel class: Capitaine Mark II
• Home port: github.com/Lucineer/capitaine
• Domain: capitaine.ai

No fake metrics. What you see is what’s running.

1. Read the concepts and tutorials.
2. Explore the fleet (more vessels coming soon).
3. Open an issue to suggest a feature, report a bug, or propose a mission.
4. Watch the repo to see the heartbeat in action.
5. Fork and build your own vessel.

MIT © Lucineer Fleet.
See LICENSE for details.

“A ship in harbor is safe, but that is not what ships are built for.”
— John A. Shedd