chronos-data-flow
Skill4 starsChanged yesterdayApache-2.0View on GitHub
Test Chronos Docker stack data flow across container states. Run to verify Core, Query Service, and MCP connectivity, health endpoints, event creation/query, and end-to-end data flow. Triggers on "test data flow", "check data flow", "chronos health", "test chronos stack", "verify containers".
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- allsource-incident-statusSkill
- allsource-partnershipsSkill
- ritual-fullSkill
- ritualSkill
- semantic-isaSkill
- admin-healthSkill
- allsource-data-accessSkill
- allsource-debugSkill
- allsource-incident-statusSkill
- allsource-mcp-setupSkill
- allsource-onboardSkill
- chronos-data-flow-embeddedSkill
- chronos-durabilitySkill
- chronos-embedded-durabilitySkill
- chronos-releaseSkill
- fly-statusSkill
- mammoth-memorySkill
- ritual-fullSkill
- ritualSkill
- semantic-isaSkill
- seo-aeo-auditSkill
- allsource-customerSkill
- allsource-prime-memorySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Run the data flow test script:
- Distinctive: line 26
If specific sections were requested, use the appropriate flag:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chronos Data Flow Test
Tests the full data flow through the Chronos Docker stack across multiple container states.
When invoked:
- Run the data flow test script:
bash tooling/data-flow-test/test-data-flow.sh - Analyze the output and report:
- Which containers are up/down
- Whether the stack is running in standalone (no PostgreSQL) or full mode
- Which tests passed, failed, or were skipped
- Root cause analysis for any failures
- If specific sections were requested, use the appropriate flag:
--state— container state only--core— Core tests only--query— Query Service tests only--mcp— MCP tests only--flow— end-to-end data flow only--json— append for machine-readable output
Test Coverage
The script tests these data flow paths:
| Test Area | What's Checked |
| Container State | Port reachability for Core (3280), Query Service (3283), MCP (3904), PostgreSQL (3284) |
| Core Health | /health, /api/v1/stats, /api/v1/events/query, /api/v1/projections, /api/v1/schemas, /api/v1/snapshots, /api/v1/topology |
| Query Service Health | /api/health, /api/health/live, /api/health/ready |
| Query Service Proxy | /api/tenant, /api/tenant/usage, /api/events, /api/events/streams, /api/events/types, /api/openapi |
| MCP | /health |
| E2E Write Path | Create event via Query Service (or Core fallback) |
| E2E Read Path | Read event back from Core, read via Query Service, verify in streams/types lists |
| Query DSL | Execute DSL query for the test entity |
Common Failure Patterns
- Core DOWN, Query Service UP: Query Service health will show
backend: degraded. Event proxy calls will fail. - Query Service DOWN, Core UP: Direct Core tests pass. Flow test falls back to writing directly to Core.
- Standalone mode (no PostgreSQL): Tenant/usage endpoints return dev tenant. Usage metering is skipped. This is expected.
- 404 on Query Service endpoints: Route mismatch — check if MCP is using
/api/v1/paths instead of/api/paths.
Environment Variables
Override default ports if your Docker mapping differs:
CORE_PORT=3280 QUERY_PORT=3283 MCP_PORT=3904 bash tooling/data-flow-test/test-data-flow.shDocker Compose
To bring the stack up/down for testing:
# Start
docker compose -f ~/Projects/alphaSigmaPro/wallet/docker/docker-compose.chronos.yml up -d
# Stop
docker compose -f ~/Projects/alphaSigmaPro/wallet/docker/docker-compose.chronos.yml downDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

