CHRONICLE A CYBERCORE SYSTEM

THE CYBERCORE REPOSITORY JOURNAL

Every repo.
Every change.
One chronicle.

Pick up exactly where you left off. Chronicle turns activity across your repositories into a compact digest of new commits, working-tree changes, and rewritten history.

Get started ↗ View source ↗

LOCAL FIRST   /   RUST + GIT   /   OPEN SOURCE

● ● ●   chronicle / activity stream PREVIEW 
$ chronicle

=== cyberdesk ===
  a42f8c1 Refine the editor layout
  working tree: 1 modified, 0 staged, 0 untracked

=== cybercore ===
  f70ba92 Add a new palette

=== field-notes ===
  history rewritten since last check

3 repo(s) total, 3 with activity to report
ILLUSTRATIVE DATA · SELECT A VIEW ABOVE CYBERCORE / 01
Git-native Real repository signals
Stateful Since your last check
Markdown An optional daily journal
Rust Small, focused CLI

01 / BUILT WITH INTENT

A place for every
meaningful change.

Tools earn their place by making the next step easier. Chronicle keeps a narrow focus: what changed in Git since your last look.

01 /

One tree. All the activity.

Discover repositories beneath configured roots, with a depth limit you control. Discovery stops at each repository boundary.

02 /

Only the new chapter.

Remember the last-seen commit for each repository and report commits since that checkpoint.

03 /

Uncommitted counts, too.

See modified, staged, and untracked counts alongside committed work. Loose ends stay visible.

04 /

Rewrites are a signal.

Report history changes that cannot be represented as a linear list of new commits.

05 /

A journal that accumulates.

Append timestamped Markdown digests to a daily file. GitHub origins produce clickable commit links.

06 /

Quiet when nothing moved.

Unchanged, clean repositories stay out of the digest unless you request them with --show-unchanged.

02 / IN YOUR ELEMENT

Less catching up.
More moving forward.

A checkpoint, a comparison, a useful digest. The rhythm stays simple as your repository tree grows.

Explore the implementation ↗

Choose the territory.

Configure one or more repository roots and a maximum discovery depth.

Establish your checkpoint.

The first run records each repository’s HEAD. Subsequent runs compare against saved state.

Read the next chapter.

Run Chronicle again for a new digest. Use your own scheduler if you want periodic reports.

03 / MAKE IT YOURS

Your next session
starts here.

Bring Rust and Git. These Linux commands use sibling checkouts and adjust the published manifest’s machine-specific Cybercore path. Then add a configuration file for your repository roots.

TERMINAL / INSTALL 
# Run from a new workspace directory
git clone https://github.com/cybercoretech/cybercore.git
git clone https://github.com/cybercoretech/chronicle.git
cd chronicle
# Make the published manifest's local dependency portable (Linux):
sed -i 's|/home/raven/.sysops/cybercore|../cybercore|' Cargo.toml
cargo install --path . --locked
mkdir -p "$HOME/.config/chronicle"
# Save the configuration below as ~/.config/chronicle/config.toml
chronicle

CONFIG.TOML / THE ESSENTIALS

CONFIGURATION 
state_path = "~/.local/state/chronicle/state.json"
max_depth = 3
markdown_out_dir = "~/Notes/Chronicle"

[[root]]
path = "~/Devspace"

Set root paths to your own repository directories. --config selects another configuration file; --no-color disables terminal colors.

Does it scan inside each repository?

Discovery stops when it finds a .git directory or file. Chronicle reads Git state rather than monitoring every filesystem write.

Does it run in the background?

Each invocation scans, reports, and updates its checkpoint. Schedule the command yourself for periodic digests.

What should I know about roots and history?

Overlapping roots are not deduplicated. A rewritten history is flagged, but Chronicle does not reconstruct the rewrite. GitHub commit links require a GitHub origin.

PART OF THE CYBERCORE FAMILY

Independent tools.
One shared language.

Explore Cybercore ↗ Meet Cyberdesk ↗
dev@cybercoretech.net