Skip to content

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

16 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

summit

The meta-repository for automating cross-repository work across the Spine SDK.

summit is a Git superproject: it assembles the Spine SDK repositories as submodules in a single working tree, so agents and the shared config/CI tooling can act across the whole SDK at once. It ships no code and has no build of its own — its content is the pinned commits of the submodules below, plus the shared agent tooling under .agents/.

Repository layout

The submodules are pinned to fixed commits, giving a reproducible snapshot of the SDK. They are grouped below by function, not by strict dependency order.

Shared infrastructure

Submodule Role
config Dependencies and build configurations shared among subprojects

The shared agent tooling — skills, scripts, and guidelines — lives in the agents repository, mounted at .agents/shared. Unlike the submodules listed here, that mount floats to the tip of master rather than a pinned commit. The same repository is also wired in as a pinned top-level submodule at agents/, so cross-repository automation can run against the tooling repo itself, just as it does against the SDK repositories above.

Foundation & utilities

Submodule Role
base-libraries The framework's base types and utilities
reflect Utilities for working with reflection in Java and Kotlin projects
logging Fluent logging API for Kotlin projects
testlib Testing utilities for Spine SDK development and users

Domain & value types

Submodule Role
base-types Popular value object types and associated code
change Data types and utilities for changes and mismatches in data values
time Protobuf-based date/time types and utilities
money Currency and money data types and operations

Compiler & code generation

Submodule Role
compiler The Spine Compiler — extendable Protobuf compilation
tool-base Common code for development tools
ProtoTap Utilities for tapping protoc output
validation Library and Compiler plugins for generating custom validation code
core-jvm-compiler Plugins of the CoreJvm library for the Spine Compiler

Framework core

Submodule Role
core-jvm The JVM-based implementation of the Spine framework core

Storage & runtime

Submodule Role
jdbc-storage Support for storage in JDBC-compliant databases
gcloud-jvm Support for Spine-based Kotlin and Java apps on Google Cloud

Getting started

Clone with all submodules in one step:

git clone --recursive https://github.com/SpineEventEngine/summit.git

If you cloned without --recursive, or you are working in a fresh git worktree or a shallow checkout, the submodules start uninitialised and the .agents symlinks dangle. Bootstrap them with:

./init-submodules   # materialise the config-managed submodules at their pinned commits
./config/pull       # float the shared submodules and copy in the shared files

./init-submodules runs automatically at the start of a Claude Code session. See AGENTS.md for the full bootstrap chain and the rationale behind it.

Working across repositories

summit is where cross-repository work happens: coordinated agent sessions and the shared config tooling propagate changes — dependency bumps, CI workflows, agent guidelines — across the SDK from one place. Agent orientation, safety rules, and the available skills are described in AGENTS.md.

License

summit, like the rest of the Spine SDK, is distributed under the Apache License 2.0.

About

The repository for automation of cross-repository works

Resources

Code of conduct

Contributing

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages