GitHub Repositories

Real, shipped code backs the AI extensions and the execution engine. It lives in the github.com/visicore organization. The repositories below drive this initiative.

The X10 GitHub Project is the official tracker for this work. Milestones, the delivery worklist, and issue status all live there.

1. VisiCore Open-Source Tools

• What it is: Our public GitHub repositories. They hold configuration helpers, scripts, and validation tools.
• How it's used: Our consultants use them to automate deployments. We leave them behind for the customer's team.
• Why it matters: It is the trusted platform we attach AI extensions to. So we do not have to build a new platform from scratch.

2. X10

• What it is: The live portal (portal.visicoretech.com) and this very documentation site.
• How it's used: Customers use it today to submit tickets, book time, and connect their environments.
• Why it matters: The customer-facing surface for tickets, scheduling, and connectors. AI extensions attach to it directly.

3. vct-cribl-cli

• What it is: The delivery engine. It is an MIT-licensed CLI that covers all 68 Cribl Cloud REST resource categories, with MCP endpoints.
• How it's used: Vizzy and VisiCore engineers compose commands through it. Every change runs --dry-run before an engineer approves it. Customers keep it after a setup-and-enablement engagement.
• Why it matters: It is the integration layer VisiCore owns. Whoever owns the integration layer owns the delivery economics.

4. vct-splunk-cli

• What it is: The Splunk counterpart to the Cribl CLI. It works end to end and is in polish before its first client engagement.
• How it's used: It gives the same compose, dry-run, and approve loop against Splunk APIs. So VisiCore owns the integration layer for both platforms.
• Why it matters: One vendor-agnostic layer sits under Vizzy. We can extend it to the next platform after Splunk.

5. vct-cribl-pack-validator

• What it is: A tool that automatically checks Cribl Packs against best practices and security standards.
• How it's used: It makes sure that any Cribl configuration, whether made by AI or by a person, meets VisiCore's strict quality bar before deployment.
• Why it matters: It acts as an automated "Config Audit" layer inside the Health Assessment and agentic workflow.

6. cc-edge-claude-code-otel

• What it is: OpenTelemetry instrumentation for AI tools like Claude Code.
• How it's used: It emits traces and telemetry data while the AI runs.
• Why it matters: It is essential for internal monitoring. It tracks how much time AI saves, or costs in review time. That lets us measure COGS (Cost of Goods Sold) accurately before we quote ROI to customers.