Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
30 commits
Select commit Hold shift + click to select a range
20b2ce0
Record public GitHub data-plane bootstrap
May 5, 2026
172eb87
Add public repo navigation docs
May 5, 2026
b236946
Add public issue templates and owner indexes
May 5, 2026
655379e
Archive root witness manifests
May 5, 2026
1acffc6
Polish public landing README
May 5, 2026
ea87284
Sharpen public landing README
May 5, 2026
0955ebd
Add encyclopedia link to landing README
May 5, 2026
9ece32e
Polish public GitHub docs entry points
May 5, 2026
beb0edd
Add sandbox return intake support
May 5, 2026
2eaf984
Evolve ChatOps browser extension cockpit
May 5, 2026
4eed0d6
Restore JOC cockpit shell support files
May 5, 2026
3a05007
Record queue hygiene and runtime evidence
May 5, 2026
03d49e2
Clarify role true names and operational titles
May 5, 2026
4f04454
fix(extension): add safe mode and throttle ChatGPT DOM scanner
May 5, 2026
ad1fc2d
Document volatile live-state branch policy
May 5, 2026
0618a82
Refine ChatOps composer cockpit layout
May 5, 2026
e90ecab
Add guarded ChatOps artifact attachment lane
May 5, 2026
42657a5
Polish ChatOps composer anchoring and capture badges
May 5, 2026
00fba0e
Add local operator artifact attach lane
May 5, 2026
8f6decb
Repair local artifact attach and composer drawer
May 5, 2026
1fdd93f
Instrument local attach target geometry
May 5, 2026
24edd8c
Add ChatOps attach target calibration
May 5, 2026
d570489
Make ChatOps artifact drop zone explicit
May 5, 2026
38fcbf1
Clean up ChatOps synthetic drop overlay
May 5, 2026
9334cf7
Add stable tunnel plan and connector landing page
May 5, 2026
77c4790
Harden stable tunnel health checks
May 6, 2026
9560f13
Expand ION public docs spine
May 6, 2026
aa1c588
Add reproducible ION product package scaffold
May 6, 2026
ddd589f
Refine product package first-run continuity UX
May 6, 2026
556d006
Add product package engine coverage manifest
May 6, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
blank_issues_enabled: true
contact_links:
- name: Security or secret exposure
url: https://github.com/ION-operations/ion-codex/security/advisories/new
about: Report secrets, credentials, or sensitive vulnerabilities privately.

69 changes: 69 additions & 0 deletions .github/ISSUE_TEMPLATE/ion_work_packet.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,69 @@
name: ION work packet
description: Propose a bounded ION work item with proof and authority boundaries.
title: "[ION Work] "
labels:
- ion-work
body:
- type: markdown
attributes:
value: |
Use this for public, non-secret work proposals. GitHub issues are discussion and data-plane evidence; they do not directly become accepted ION state.
- type: textarea
id: objective
attributes:
label: Objective
description: What should change or be investigated?
placeholder: Build, fix, audit, document, or analyze a bounded ION surface.
validations:
required: true
- type: textarea
id: owner_surfaces
attributes:
label: Existing owner surfaces
description: List files or directories that should own this work.
placeholder: |
ION/02_architecture/...
ION/03_registry/...
ION/04_packages/kernel/...
ION/tests/...
validations:
required: true
- type: dropdown
id: output_type
attributes:
label: Output type
options:
- protocol/docs
- registry/template update
- bounded implementation patch
- tests/validation
- receipt/evidence
- question/review
validations:
required: true
- type: checkboxes
id: boundaries
attributes:
label: Authority boundaries
options:
- label: This does not request production deployment.
required: true
- label: This does not request secrets, credentials, or private logs.
required: true
- label: This does not request direct push to main.
required: true
- label: This should preserve ION packet, receipt, and proof-gate principles.
required: true
- type: textarea
id: validation
attributes:
label: Expected validation
placeholder: |
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=ION/04_packages python3 -S -m kernel.ion_status --ion-root . --json
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=ION/04_packages PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python3 -m pytest ION/tests -q
- type: textarea
id: notes
attributes:
label: Notes, links, or receipts
description: Add non-secret context, GitHub refs, ION receipt paths, or prior discussion links.

45 changes: 45 additions & 0 deletions .github/ISSUE_TEMPLATE/public_bug_report.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
name: Public bug report
description: Report a non-sensitive problem in the public ION Codex repo.
title: "[Bug] "
labels:
- bug
body:
- type: markdown
attributes:
value: |
Do not include secrets, credentials, private logs, tokens, or production-only state. Use a security advisory for sensitive reports.
- type: textarea
id: summary
attributes:
label: Summary
description: What is wrong?
validations:
required: true
- type: textarea
id: steps
attributes:
label: Reproduction or evidence
description: Include commands, paths, screenshots, or public logs when safe.
placeholder: |
Command:
Expected:
Actual:
validations:
required: true
- type: textarea
id: affected_paths
attributes:
label: Affected paths
placeholder: |
ION/04_packages/kernel/...
ION/09_integrations/...
- type: checkboxes
id: safety
attributes:
label: Safety check
options:
- label: I did not include secrets, credentials, tokens, private logs, or production-only state.
required: true
- label: I understand this issue is public.
required: true

33 changes: 33 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
# Summary

Describe the bounded change and the owner surfaces reused.

## ION Boundaries

- Production authority: false
- Live external execution authority: false
- Secrets or credentials included: no
- Direct `main` push requested: no
- Branch trust class: review | volatile / not trusted | stable promotion

## Touched Paths

```text

```

## Validation

```text

```

## Receipts Or Evidence

```text

```

## Notes

List known blockers, skipped checks, or follow-up work.
115 changes: 115 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,115 @@
# Contributing

This repository is public for collaboration, but ION state is still governed by
packets, receipts, proof gates, and bounded carrier authority.

## Start Here

Read the public landing page first:

- `README.md`

Then use the docs layer for the shape of the system:

- `ION/docs/README.md`
- `ION/docs/GITHUB_BRANCHING_AND_LIVE_STATE_POLICY.md`
- `ION/docs/ION_FUNDAMENTALS.md`
- `ION/docs/ION_DOMAIN_GRAPH_AND_FISSION.md`
- `ION/docs/ION_PARALLEL_SETTLEMENT.md`
- `ION/docs/ION_PROJECT_INGESTION.md`
- `ION/docs/TEMPLATE_LAW.md`
- `ION/docs/CONTEXT_SYSTEM.md`
- `ION/docs/AGENTS_ROLES_CARRIERS.md`

Use the encyclopedia for broad history and architecture:

- `ION/docs/encyclopedia/ION_Production_Encyclopedia_v4_0_LIVE_V96_V100_CONTEXT_SYSTEM_AND_AUTONOMOUS_LOOP_RECOVERY.md`

The encyclopedia is reference material, not active runtime authority.

## Before You Change Files

1. Read `ION/REPO_AUTHORITY.md`.
2. Use a scoped branch:
- `docs/<short-topic>`
- `work/<short-topic>`
- `agent/<short-topic>`
- `data-plane/<short-topic>`
- `volatile/live-YYYYMMDD-<short-topic>` for public live-state snapshots
that are useful for collaboration but not yet trusted ION state.
3. Keep changes narrow and explain the owner surface you reused.
4. Run the smallest meaningful validation for the change.
5. Open a pull request with evidence.

## Contribution Lanes

Use the smallest lane that matches the work:

| Lane | Good for |
| --- | --- |
| Docs | README, guides, explanation, public navigation. |
| Kernel | Python runtime, tests, audits, gates, queue projections. |
| Integration | MCP, browser extension, daemon, Cursor, Codex carrier surfaces. |
| Context evidence | Receipts, work packets, queue settlement, lifecycle records. |
| Project ingestion | Quarantine, manifests, cartography, domain partition, first context packages. |

Keep public docs, runtime implementation, and active-state evidence in separate
pull requests when possible. That makes review and future indexing cleaner.

## Volatile Live Branches

ION can use `volatile/*` branches to show the real local project posture to
other humans and AI carriers. These branches may move quickly and may contain
still-settling code, docs, and non-secret evidence.

They must be labeled as:

```text
VOLATILE / NOT TRUSTED ION STATE
```

Do not treat a volatile branch as Steward acceptance, production authority, or
runtime truth. It is visibility for collaboration. Promotion still requires the
normal packet, proof, gate, review, and receipt path.

Never commit secrets, credentials, private connector auth state, private browser
profiles, or sensitive live tunnel material to a volatile branch. Live connector
URLs and logs should stay local unless they are intentionally public-safe and
useful as redacted evidence.

## Pull Request Evidence

Include:

- objective
- touched paths
- validations run
- known blockers or skipped checks
- relevant ION packet, receipt, issue, branch, or artifact references

## What Not To Submit

- secrets, credentials, tokens, private browser profiles, tunnel credentials, or
`.env` files
- production deployment changes unless explicitly authorized by ION policy and
Braden
- broad rewrites that bypass existing architecture, registry, packet, or
receipt owners
- raw AI output as accepted state without proof-gated integration

## Validation Commands

Useful defaults from the shell root:

```bash
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=ION/04_packages python3 -S -m kernel.ion_status --ion-root . --json
PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=ION/04_packages PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 python3 -m pytest ION/tests -q
```

## GitHub Is A Data Plane

GitHub issues and pull requests are collaboration surfaces. They do not grant
runtime authority, production authority, secret authority, or Steward
acceptance by themselves. Accepted state still requires the ION proof path:
packet, context, template, proof-bearing return, gate, Steward decision, and
receipt.
Loading