| Name | cccc-pair JSON |
| Version |
0.2.5
JSON |
| download |
| home_page | None |
| Summary | Two‑AI orchestrator (tmux) for evidence‑first, small‑step collaboration |
| upload_time | 2025-09-05 05:36:00 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.9 |
| license | Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
|
| keywords |
orchestrator
tmux
ai
rfd
pair
collaboration
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# CCCC Pair — Dual‑AI Orchestrator (Telegram‑first, Evidence‑first)
Two best‑in‑class AI CLIs (Claude Code + Codex CLI) co‑drive your work as equal peers. They collaborate, self‑review, and ship small, reversible changes with built‑in governance. You monitor and approve from two places: tmux or your team’s Telegram chat.
Not a chatbot UI. Not an IDE plugin. A production‑minded orchestrator for 24/7, long‑running work.
## Why It’s Different
- Dual‑AI Autonomy: peers continuously plan → build → critique → refine. They don’t wait for prompts; they follow a mailbox contract and change the world only with EVIDENCE (diff/tests/logs/benchmarks).
- Telegram‑first Collaboration: a 24/7 agent lives in your team chat. High‑signal summaries, one‑tap RFD decisions, explicit routing (a:/b:/both:) so normal conversation remains normal. Files flow both ways with captions and sidecars.
- Builder–Critic Synergy: peers challenge CLAIMs with COUNTERs and converge via verifiable EVIDENCE. In practice this beats single‑model quality on complex, multi‑day tasks.
- tmux Transparency: dual panes (PeerA/PeerB) + compact status panel. You can peek, nudge, or inject text without disrupting flows—and without a GUI.
- Governance at the Core (RFD): protected areas and irreversible changes raise Request‑For‑Decision cards in chat; approvals are written to a ledger and unlock execution.
- Team‑level Efficiency: one always‑on bot concentrates orchestration and approvals for the whole team. You reduce duplicated “per‑seat” sessions and still retain control.
## What You Get
- Evidence‑first loop: tiny diffs/tests/logs; only green changes commit.
- Single‑branch queue: preflight `git apply` → (optional) lint/tests → commit.
- RFD closed loop: generate cards, gate protected paths/large diffs, unlock on decision.
- Telegram integration: explicit routing; `/status`, `/queue`, `/locks`, `/rfd list|show`, `/showpeers on|off`, file send/receive with meta.
- Ledger: append‑only `.cccc/state/ledger.jsonl` (patch/test/log/decision) for audit.
## Requirements
- Python `>= 3.9`
- tmux (e.g., `brew install tmux` or `sudo apt install tmux`)
- git (preflight/commits)
Supported CLIs (current)
- Peer A: Claude Code CLI (recommended: MAX Plan)
- Peer B: Codex CLI (recommended: PRO Plan)
## Install
- Recommended (pipx)
- `pipx install cccc-pair`
- Or venv
- `python3 -m venv v && . v/bin/activate && pip install cccc-pair`
## Quick Start (5 minutes)
1) Initialize in your project repo
```
cccc init
```
This copies the scaffold to `./.cccc/` and appends `/.cccc/**` to `.gitignore` (Ephemeral).
2) Check environment
```
cccc doctor
```
3) (Optional) Enable Telegram
```
cccc token set # paste your bot token; stored in .cccc/settings/telegram.yaml (gitignored)
```
4) Run orchestrator (tmux UI)
```
cccc run
```
tmux opens: left/right = PeerA/PeerB, bottom‑right = status panel. If token is present and autostart=true, the Telegram bridge starts automatically.
5) First‑time CLI setup (required)
- Install the two CLIs and make sure the binaries are on PATH:
- `claude ...` (Claude Code)
- `codex ...` (Codex CLI)
- Paste system prompts for best collaboration quality:
- Open `PEERA.md` and copy its full content into a new file `CLAUDE.md` at your repo root (not tracked; `.gitignore` already ignores it). Claude Code CLI should load this as its system prompt.
- Open `PEERB.md` and copy its full content into a new file `AGENTS.md` at your repo root (not tracked). Codex CLI should load this as its system prompt.
- Move any previous “project state” prompt into `PROJECT.md` at the repo root (recommended). The orchestrator will weave this into the runtime SYSTEM so both peers align on scope and goals.
- Verify or adjust the CLI commands in `.cccc/settings/cli_profiles.yaml`:
- `commands.peerA: "claude ..."`
- `commands.peerB: "codex ..."`
- You can also override at runtime with env vars: `CLAUDE_I_CMD`, `CODEX_I_CMD`.
## First Landing Checklist (Minimal)
Do just these to get a clean, working setup:
1) `cccc init` (creates `./.cccc` and ignores runtime dirs)
2) `cccc doctor` (git/tmux/python)
3) Prepare system prompts (required once per repo)
- Copy `PEERA.md` → `CLAUDE.md` (root)
- Copy `PEERB.md` → `AGENTS.md` (root)
- Put your brief/scope in `PROJECT.md` (root)
4) Optional Telegram (highly recommended)
- `cccc token set`
- `cccc run` (bridge autostarts) or `cccc bridge start`
5) Start work: `cccc run` (tmux panes + status panel)
That’s it. You can refine policies later.
## Telegram Quickstart (Team Hub)
- Group routing: use explicit routes so normal chat stays normal
- `a: <text>` / `b: <text>` / `both: <text>`
- or `/a ...` `/b ...` `/both ...` (works with privacy mode)
- Get oriented
- `/status` project stats; `/queue` handoff queue; `/locks` internal locks
- `/whoami` shows your chat_id; `/subscribe` (if `autoregister: open`)
- `/showpeers on|off` toggles Peer↔Peer summaries
- File exchange
- Outbound (AIs → Telegram): save under `.cccc/work/upload/outbound/<peer>/{photos,files}/`
- Optional caption: same‑name `.caption.txt`; force send‑as via `.sendas` (`photo|document`)
- Sent files are deleted on success; `outbound.reset_on_start: clear` avoids blasting residuals on restart
- Inbound (Telegram → AIs): bot writes `<FROM_USER>` with sidecar meta; peers act on it
- Governance: RFD cards in chat with Approve/Reject; decisions go to the ledger and unlock execution.
## A Typical Session (End‑to‑End, ~3 minutes)
Goal: ship a small, reversible change with dual‑AI collaboration.
1) Explore (short)
- In Telegram (or tmux), route a brief idea to both: `both: Add a section to README about team chat tips`
- PeerA summarizes intent; PeerB asks 1 focused question if needed.
2) Decide (concise CLAIM)
- PeerA writes a CLAIM in `peerA/to_peer.md` with acceptance and constraints (≤150 lines; links to where to edit).
- PeerB COUNTERs if there’s a sharper place or a safer rollout.
3) Build (evidence‑first)
- PeerB produces a tiny unified diff in `peerB/patch.diff` (e.g., add a new README subsection) and a 1–2 line EVIDENCE note (tests OK/lines/paths/MID).
- Orchestrator preflights → applies → (optional) lint/tests → commits on green and logs to ledger.
4) Team visibility
- Telegram posts a concise summary (debounced); peers stay quiet unless blocked.
- If you need files (screenshots/spec PDFs), drop them to the bot with a caption; peers act on the inbound block with meta.
RFD is not required here. It triggers automatically only for protected areas or when you explicitly ask for a decision.
## Recommended Stack (Pragmatic & Stable)
- AI CLIs: Claude Code (MAX Plan) + Codex CLI (PRO Plan) for robust, sustained workloads.
- Orchestrator: this project, with tmux for long‑lived panes and a compact panel.
- Transport & Governance: Telegram for team‑wide visibility, quick RFD decisions, and file exchange.
## Folder Layout (after `cccc init`)
```
.cccc/
adapters/telegram_bridge.py # Telegram long‑poll bridge (MVP)
settings/
cli_profiles.yaml # tmux/paste/type behavior; echo; idle regexes; self‑check
policies.yaml # patch queue size; allowlist; RFD gates
roles.yaml # leader; specialties; rotation
telegram.yaml # token/autostart/allowlist/dry_run/routing/files
mailbox/ # peerA/peerB with to_user.md/to_peer.md/patch.diff; inbox/processed
work/ # shared workspace; upload inbound/outbound; ephemeral
state/ # ledger.jsonl, bridge logs, status/session; ephemeral
logs/ # extra logs; ephemeral
orchestrator_tmux.py delivery.py mailbox.py panel_status.py prompt_weaver.py
evidence_runner.py mock_agent.py
```
## CLI Reference
- `cccc init [--force] [--to PATH]` — copy scaffold; preserves layout; excludes runtime dirs
- `cccc doctor` — check git/tmux/python/telegram
- `cccc run` — start orchestrator (tmux panes + status panel; autostarts bridge when configured)
- `cccc token set|unset|show` — manage Telegram token (gitignored)
- `cccc bridge start|stop|status|restart|logs [-n N] [--follow]` — control and inspect bridge
- `cccc clean` — purge `.cccc/{mailbox,work,logs,state}/`
- `cccc version` — show package version and scaffold path info
CLI prerequisites (summary)
- Peer A = Claude Code; Peer B = Codex CLI. Install and log in as required by each vendor.
- Ensure the binaries (`claude`, `codex`) are on PATH or set `commands.peer*`/`CLAUDE_I_CMD`/`CODEX_I_CMD`.
## Key Configuration (snippets)
`.cccc/settings/policies.yaml`
```
patch_queue:
max_diff_lines: 150
allowed_paths: ["src/**","tests/**","docs/**","infra/**","README.md","PROJECT.md"]
rfd:
gates:
protected_paths: [".cccc/**","src/api/public/**"]
large_diff_requires_rfd: false
handoff_filter:
enabled: true
cooldown_seconds: 15
```
`.cccc/settings/telegram.yaml`
```
token_env: "TELEGRAM_BOT_TOKEN"
autostart: true
discover_allowlist: true
autoregister: open
dry_run: false
files:
enabled: true
outbound_dir: ".cccc/work/upload/outbound"
outbound:
reset_on_start: clear
```
## FAQ / Troubleshooting
**tmux panes not appearing?**
- Install tmux (`tmux -V`), run in a TTY, then `cccc run`. Check `cccc doctor`.
**Telegram bot silent?**
- `cccc token show` (token saved?) → `cccc bridge status` (running?) → `cccc bridge logs -n 200`
- In group chats, route explicitly (`a:`/`/a`), and run `/whoami` or `/subscribe` once to register
- Ensure `autostart: true`, `dry_run: false`
**Claude/Codex CLI not found?**
- Install the CLIs and make sure the binaries are on PATH; otherwise set explicit commands:
- Edit `.cccc/settings/cli_profiles.yaml` (`commands.peerA|peerB`) or
- Export env vars before `cccc run`: `CLAUDE_I_CMD="/path/to/claude ..."`, `CODEX_I_CMD="/path/to/codex ..."`
**Where to put my project brief/policies?**
- Put your project scope/brief in `PROJECT.md` (repo root). The orchestrator injects it into the runtime SYSTEM so both peers align.
- RFD/protected paths live in `.cccc/settings/policies.yaml`.
**“This environment is externally managed” during install/build?**
- Use a venv or pipx for publishing; avoid system Python for `pip install` of tools like build/twine.
**RFD card not shown?**
- Confirm ledger has `kind:rfd`; check bridge logs; verify gates and to_peer YAML format.
## Security & Privacy
- Telegram token saved to `.cccc/settings/telegram.yaml` (gitignored) or env; do not commit secrets.
- Bridge redacts common secret patterns; keep mailbox content free of tokens.
- Orchestrator domain `.cccc/**` is runtime; do not commit `state/logs/work/mailbox`.
## Roadmap (Selected)
- Role‑based approvals; multi‑sign gates; richer RFD templates with default options/expiry
- Artifact previews in chat; repro snippets; CI/CD hooks for release/rollback cards
- Optional safety scanners (ClamAV/DLP) for inbound files; Slack/Mattermost bridges
## License
Apache (see LICENSE).
Raw data
{
"_id": null,
"home_page": null,
"name": "cccc-pair",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": "orchestrator, tmux, ai, rfd, pair, collaboration",
"author": null,
"author_email": "ChesterRa <ra@ike.ba>",
"download_url": "https://files.pythonhosted.org/packages/b1/a6/f1a0ead4238c19db055a0f9dbf94bc7e18c65f27a6f16103ceb61bd228f4/cccc_pair-0.2.5.tar.gz",
"platform": null,
"description": "# CCCC Pair \u2014 Dual\u2011AI Orchestrator (Telegram\u2011first, Evidence\u2011first)\n\nTwo best\u2011in\u2011class AI CLIs (Claude Code + Codex CLI) co\u2011drive your work as equal peers. They collaborate, self\u2011review, and ship small, reversible changes with built\u2011in governance. You monitor and approve from two places: tmux or your team\u2019s Telegram chat.\n\nNot a chatbot UI. Not an IDE plugin. A production\u2011minded orchestrator for 24/7, long\u2011running work.\n\n## Why It\u2019s Different\n\n- Dual\u2011AI Autonomy: peers continuously plan \u2192 build \u2192 critique \u2192 refine. They don\u2019t wait for prompts; they follow a mailbox contract and change the world only with EVIDENCE (diff/tests/logs/benchmarks).\n- Telegram\u2011first Collaboration: a 24/7 agent lives in your team chat. High\u2011signal summaries, one\u2011tap RFD decisions, explicit routing (a:/b:/both:) so normal conversation remains normal. Files flow both ways with captions and sidecars.\n- Builder\u2013Critic Synergy: peers challenge CLAIMs with COUNTERs and converge via verifiable EVIDENCE. In practice this beats single\u2011model quality on complex, multi\u2011day tasks.\n- tmux Transparency: dual panes (PeerA/PeerB) + compact status panel. You can peek, nudge, or inject text without disrupting flows\u2014and without a GUI.\n- Governance at the Core (RFD): protected areas and irreversible changes raise Request\u2011For\u2011Decision cards in chat; approvals are written to a ledger and unlock execution.\n- Team\u2011level Efficiency: one always\u2011on bot concentrates orchestration and approvals for the whole team. You reduce duplicated \u201cper\u2011seat\u201d sessions and still retain control.\n\n## What You Get\n\n- Evidence\u2011first loop: tiny diffs/tests/logs; only green changes commit.\n- Single\u2011branch queue: preflight `git apply` \u2192 (optional) lint/tests \u2192 commit.\n- RFD closed loop: generate cards, gate protected paths/large diffs, unlock on decision.\n- Telegram integration: explicit routing; `/status`, `/queue`, `/locks`, `/rfd list|show`, `/showpeers on|off`, file send/receive with meta.\n- Ledger: append\u2011only `.cccc/state/ledger.jsonl` (patch/test/log/decision) for audit.\n\n## Requirements\n\n- Python `>= 3.9`\n- tmux (e.g., `brew install tmux` or `sudo apt install tmux`)\n- git (preflight/commits)\n\nSupported CLIs (current)\n- Peer A: Claude Code CLI (recommended: MAX Plan)\n- Peer B: Codex CLI (recommended: PRO Plan)\n\n## Install\n\n- Recommended (pipx)\n - `pipx install cccc-pair`\n- Or venv\n - `python3 -m venv v && . v/bin/activate && pip install cccc-pair`\n\n## Quick Start (5 minutes)\n\n1) Initialize in your project repo\n\n```\ncccc init\n```\n\nThis copies the scaffold to `./.cccc/` and appends `/.cccc/**` to `.gitignore` (Ephemeral).\n\n2) Check environment\n\n```\ncccc doctor\n```\n\n3) (Optional) Enable Telegram\n\n```\ncccc token set # paste your bot token; stored in .cccc/settings/telegram.yaml (gitignored)\n```\n\n4) Run orchestrator (tmux UI)\n\n```\ncccc run\n```\n\ntmux opens: left/right = PeerA/PeerB, bottom\u2011right = status panel. If token is present and autostart=true, the Telegram bridge starts automatically.\n\n5) First\u2011time CLI setup (required)\n\n- Install the two CLIs and make sure the binaries are on PATH:\n - `claude ...` (Claude Code)\n - `codex ...` (Codex CLI)\n- Paste system prompts for best collaboration quality:\n - Open `PEERA.md` and copy its full content into a new file `CLAUDE.md` at your repo root (not tracked; `.gitignore` already ignores it). Claude Code CLI should load this as its system prompt.\n - Open `PEERB.md` and copy its full content into a new file `AGENTS.md` at your repo root (not tracked). Codex CLI should load this as its system prompt.\n- Move any previous \u201cproject state\u201d prompt into `PROJECT.md` at the repo root (recommended). The orchestrator will weave this into the runtime SYSTEM so both peers align on scope and goals.\n- Verify or adjust the CLI commands in `.cccc/settings/cli_profiles.yaml`:\n - `commands.peerA: \"claude ...\"`\n - `commands.peerB: \"codex ...\"`\n - You can also override at runtime with env vars: `CLAUDE_I_CMD`, `CODEX_I_CMD`.\n\n## First Landing Checklist (Minimal)\n\nDo just these to get a clean, working setup:\n\n1) `cccc init` (creates `./.cccc` and ignores runtime dirs)\n2) `cccc doctor` (git/tmux/python)\n3) Prepare system prompts (required once per repo)\n - Copy `PEERA.md` \u2192 `CLAUDE.md` (root)\n - Copy `PEERB.md` \u2192 `AGENTS.md` (root)\n - Put your brief/scope in `PROJECT.md` (root)\n4) Optional Telegram (highly recommended)\n - `cccc token set`\n - `cccc run` (bridge autostarts) or `cccc bridge start`\n5) Start work: `cccc run` (tmux panes + status panel)\n\nThat\u2019s it. You can refine policies later.\n\n## Telegram Quickstart (Team Hub)\n\n- Group routing: use explicit routes so normal chat stays normal\n - `a: <text>` / `b: <text>` / `both: <text>`\n - or `/a ...` `/b ...` `/both ...` (works with privacy mode)\n- Get oriented\n - `/status` project stats; `/queue` handoff queue; `/locks` internal locks\n - `/whoami` shows your chat_id; `/subscribe` (if `autoregister: open`)\n - `/showpeers on|off` toggles Peer\u2194Peer summaries\n- File exchange\n - Outbound (AIs \u2192 Telegram): save under `.cccc/work/upload/outbound/<peer>/{photos,files}/`\n - Optional caption: same\u2011name `.caption.txt`; force send\u2011as via `.sendas` (`photo|document`)\n - Sent files are deleted on success; `outbound.reset_on_start: clear` avoids blasting residuals on restart\n - Inbound (Telegram \u2192 AIs): bot writes `<FROM_USER>` with sidecar meta; peers act on it\n- Governance: RFD cards in chat with Approve/Reject; decisions go to the ledger and unlock execution.\n\n## A Typical Session (End\u2011to\u2011End, ~3 minutes)\n\nGoal: ship a small, reversible change with dual\u2011AI collaboration.\n\n1) Explore (short)\n- In Telegram (or tmux), route a brief idea to both: `both: Add a section to README about team chat tips`\n- PeerA summarizes intent; PeerB asks 1 focused question if needed.\n\n2) Decide (concise CLAIM)\n- PeerA writes a CLAIM in `peerA/to_peer.md` with acceptance and constraints (\u2264150 lines; links to where to edit).\n- PeerB COUNTERs if there\u2019s a sharper place or a safer rollout.\n\n3) Build (evidence\u2011first)\n- PeerB produces a tiny unified diff in `peerB/patch.diff` (e.g., add a new README subsection) and a 1\u20132 line EVIDENCE note (tests OK/lines/paths/MID).\n- Orchestrator preflights \u2192 applies \u2192 (optional) lint/tests \u2192 commits on green and logs to ledger.\n\n4) Team visibility\n- Telegram posts a concise summary (debounced); peers stay quiet unless blocked.\n- If you need files (screenshots/spec PDFs), drop them to the bot with a caption; peers act on the inbound block with meta.\n\nRFD is not required here. It triggers automatically only for protected areas or when you explicitly ask for a decision.\n\n## Recommended Stack (Pragmatic & Stable)\n\n- AI CLIs: Claude Code (MAX Plan) + Codex CLI (PRO Plan) for robust, sustained workloads.\n- Orchestrator: this project, with tmux for long\u2011lived panes and a compact panel.\n- Transport & Governance: Telegram for team\u2011wide visibility, quick RFD decisions, and file exchange.\n\n## Folder Layout (after `cccc init`)\n\n```\n.cccc/\n adapters/telegram_bridge.py # Telegram long\u2011poll bridge (MVP)\n settings/\n cli_profiles.yaml # tmux/paste/type behavior; echo; idle regexes; self\u2011check\n policies.yaml # patch queue size; allowlist; RFD gates\n roles.yaml # leader; specialties; rotation\n telegram.yaml # token/autostart/allowlist/dry_run/routing/files\n mailbox/ # peerA/peerB with to_user.md/to_peer.md/patch.diff; inbox/processed\n work/ # shared workspace; upload inbound/outbound; ephemeral\n state/ # ledger.jsonl, bridge logs, status/session; ephemeral\n logs/ # extra logs; ephemeral\n orchestrator_tmux.py delivery.py mailbox.py panel_status.py prompt_weaver.py\n evidence_runner.py mock_agent.py\n```\n\n## CLI Reference\n\n- `cccc init [--force] [--to PATH]` \u2014 copy scaffold; preserves layout; excludes runtime dirs\n- `cccc doctor` \u2014 check git/tmux/python/telegram\n- `cccc run` \u2014 start orchestrator (tmux panes + status panel; autostarts bridge when configured)\n- `cccc token set|unset|show` \u2014 manage Telegram token (gitignored)\n- `cccc bridge start|stop|status|restart|logs [-n N] [--follow]` \u2014 control and inspect bridge\n- `cccc clean` \u2014 purge `.cccc/{mailbox,work,logs,state}/`\n- `cccc version` \u2014 show package version and scaffold path info\n\nCLI prerequisites (summary)\n- Peer A = Claude Code; Peer B = Codex CLI. Install and log in as required by each vendor.\n- Ensure the binaries (`claude`, `codex`) are on PATH or set `commands.peer*`/`CLAUDE_I_CMD`/`CODEX_I_CMD`.\n\n## Key Configuration (snippets)\n\n`.cccc/settings/policies.yaml`\n\n```\npatch_queue:\n max_diff_lines: 150\n allowed_paths: [\"src/**\",\"tests/**\",\"docs/**\",\"infra/**\",\"README.md\",\"PROJECT.md\"]\nrfd:\n gates:\n protected_paths: [\".cccc/**\",\"src/api/public/**\"]\n large_diff_requires_rfd: false\nhandoff_filter:\n enabled: true\n cooldown_seconds: 15\n```\n\n`.cccc/settings/telegram.yaml`\n\n```\ntoken_env: \"TELEGRAM_BOT_TOKEN\"\nautostart: true\ndiscover_allowlist: true\nautoregister: open\ndry_run: false\nfiles:\n enabled: true\n outbound_dir: \".cccc/work/upload/outbound\"\noutbound:\n reset_on_start: clear\n```\n\n## FAQ / Troubleshooting\n\n**tmux panes not appearing?**\n- Install tmux (`tmux -V`), run in a TTY, then `cccc run`. Check `cccc doctor`.\n\n**Telegram bot silent?**\n- `cccc token show` (token saved?) \u2192 `cccc bridge status` (running?) \u2192 `cccc bridge logs -n 200`\n- In group chats, route explicitly (`a:`/`/a`), and run `/whoami` or `/subscribe` once to register\n- Ensure `autostart: true`, `dry_run: false`\n\n**Claude/Codex CLI not found?**\n- Install the CLIs and make sure the binaries are on PATH; otherwise set explicit commands:\n - Edit `.cccc/settings/cli_profiles.yaml` (`commands.peerA|peerB`) or\n - Export env vars before `cccc run`: `CLAUDE_I_CMD=\"/path/to/claude ...\"`, `CODEX_I_CMD=\"/path/to/codex ...\"`\n\n**Where to put my project brief/policies?**\n- Put your project scope/brief in `PROJECT.md` (repo root). The orchestrator injects it into the runtime SYSTEM so both peers align.\n- RFD/protected paths live in `.cccc/settings/policies.yaml`.\n\n**\u201cThis environment is externally managed\u201d during install/build?**\n- Use a venv or pipx for publishing; avoid system Python for `pip install` of tools like build/twine.\n\n**RFD card not shown?**\n- Confirm ledger has `kind:rfd`; check bridge logs; verify gates and to_peer YAML format.\n\n## Security & Privacy\n\n- Telegram token saved to `.cccc/settings/telegram.yaml` (gitignored) or env; do not commit secrets.\n- Bridge redacts common secret patterns; keep mailbox content free of tokens.\n- Orchestrator domain `.cccc/**` is runtime; do not commit `state/logs/work/mailbox`.\n\n## Roadmap (Selected)\n\n- Role\u2011based approvals; multi\u2011sign gates; richer RFD templates with default options/expiry\n- Artifact previews in chat; repro snippets; CI/CD hooks for release/rollback cards\n- Optional safety scanners (ClamAV/DLP) for inbound files; Slack/Mattermost bridges\n\n## License\n\nApache (see LICENSE).\n",
"bugtrack_url": null,
"license": "Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n \n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n \n 1. Definitions.\n \n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n \n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n \n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n \n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n \n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n \n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n \n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n \n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n \n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n \n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n \n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n \n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n \n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n \n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n \n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n \n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n \n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n \n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n \n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n \n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n \n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n \n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n \n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n \n END OF TERMS AND CONDITIONS\n \n APPENDIX: How to apply the Apache License to your work.\n \n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n \n Copyright [yyyy] [name of copyright owner]\n \n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n \n http://www.apache.org/licenses/LICENSE-2.0\n \n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n ",
"summary": "Two\u2011AI orchestrator (tmux) for evidence\u2011first, small\u2011step collaboration",
"version": "0.2.5",
"project_urls": {
"Homepage": "https://github.com/ChesterRa/cccc",
"Issues": "https://github.com/ChesterRa/cccc/issues",
"Repository": "https://github.com/ChesterRa/cccc"
},
"split_keywords": [
"orchestrator",
" tmux",
" ai",
" rfd",
" pair",
" collaboration"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "4875fd9132f74f2767ff5e1e0ca33af3789d7d50d98efbc8dabdd9a327737748",
"md5": "cc0de39879bda0587750aab5eb0aeb31",
"sha256": "04b6a149a1490b2c4b4c9cd5d54294a4e7f0d3353faa587b69a0b712ef0a8fbf"
},
"downloads": -1,
"filename": "cccc_pair-0.2.5-py3-none-any.whl",
"has_sig": false,
"md5_digest": "cc0de39879bda0587750aab5eb0aeb31",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 151112,
"upload_time": "2025-09-05T05:35:59",
"upload_time_iso_8601": "2025-09-05T05:35:59.002582Z",
"url": "https://files.pythonhosted.org/packages/48/75/fd9132f74f2767ff5e1e0ca33af3789d7d50d98efbc8dabdd9a327737748/cccc_pair-0.2.5-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "b1a6f1a0ead4238c19db055a0f9dbf94bc7e18c65f27a6f16103ceb61bd228f4",
"md5": "a11a38aa6d190c9f4bd1a2f25d86d629",
"sha256": "c2f9d1c6ff2a6baa931f066d6ab3911bff3f824609c714a5efacab8971d5e5a5"
},
"downloads": -1,
"filename": "cccc_pair-0.2.5.tar.gz",
"has_sig": false,
"md5_digest": "a11a38aa6d190c9f4bd1a2f25d86d629",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 145873,
"upload_time": "2025-09-05T05:36:00",
"upload_time_iso_8601": "2025-09-05T05:36:00.213584Z",
"url": "https://files.pythonhosted.org/packages/b1/a6/f1a0ead4238c19db055a0f9dbf94bc7e18c65f27a6f16103ceb61bd228f4/cccc_pair-0.2.5.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-09-05 05:36:00",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "ChesterRa",
"github_project": "cccc",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "cccc-pair"
}
