VisiCore AI — Extending X10
Reference

Slack Updates

Paste-ready posts for the VisiCore Slack — kickoff, weekly status, and milestone announcements.

Slack is the high-level tracking surface everyone can see. This site is the detail behind it. Each block below uses Slack formatting. Copy the block, replace {DOCS-URL} with the deployed docs-site address, and paste. The weekly template rolls up from the GitHub issue board.

Kickoff post (one time)

*VisiCore AI — three products, one platform* :rocket:

Everything now lives in one place: {DOCS-URL}
Three projects, clear owners, live tracking. Here is the short version.

*What we are building*
• *X10 Dividend* — the savings product. An automated scan surfaces the savings in observability data and puts them in dollars. Our CLIs capture them. Monitoring keeps them. Priced at 25% of realized savings. Try the calculator: {DOCS-URL}/docs/dividend/calculator
• *Vizzy + The AI Brain* — our master consultant, on call 24/7. The AI Brain backs it with expertise from every engagement, and it gets smarter with every job. Tools are a commodity; the Brain is the moat.
• *Agentic delivery* — AI drafts, engineers approve. Routine work drops from hours to minutes, measured and recorded.

*The path, in order*
1. Savings calculator live (mid July)
2. Diagnostic processors for Splunk and Cribl (July) — the critical path
3. Assessment MVP: upload → sanitize → scan → branded report (August)
4. Vizzy security gates → pilot accounts → client beta
5. First paid engagement (Aug/Sep) → first recurring subscription (December)

*Who owns what*
Jacob — Splunk processor, assessment MVP, Splunk CLI | Andrew — Cribl processor, CLI unification, demo videos | Paul — sanitizer, uploader, REST API, security gates | Vince — validation, search finder | James — demo, collateral, first sale | Rob — Data Access Policy, GOAT nominations

Live tracker: {DOCS-URL}/docs/dividend/worklist
Questions and updates right here in the channel — everything gets folded back into the site.

Weekly status template

*VisiCore AI — week of {DATE}* :bar_chart:

*Done this week*
• {completed task — owner}

*In progress*
• {task — owner — one-line state}

*Blocked / needs a decision*
• {item — what it needs and from whom}

*Next week*
• {planned task — owner}

Milestones: D1 Calculator {state} | D2 Processors {state} | D3 Assessment MVP {state} | V1 Hardened Internal {state} | V2 Security Audit {state}
Details: {DOCS-URL}/docs/dividend/worklist

Milestone announcements (post when each lands)

Calculator live (D1)

:abacus: *The savings calculator is live.*
Enter your data sources and daily volumes. Get the estimated dollars back per year, straight from our measured benchmarks (FortiGate reduced ~74%, Zscaler reduced 50%+). This is the front door of X10 Dividend.
Try it: {DOCS-URL}/docs/dividend/calculator

Demo ready

:clapper: *The customer demo is ready.*
Vizzy runs an assessment end to end in X10. The two-minute walkthrough is recorded, and short-form videos are queued. This is what we show at CriblCon.
See it: {DOCS-URL}/docs/vizzy

Assessment MVP complete (D3)

:white_check_mark: *The X10 Dividend assessment MVP is complete.*
Diag bundle in → sanitized → processed → branded savings report out, with engineer sign-off as the gate. Both the Splunk and Cribl processors are live behind X10.
The product: {DOCS-URL}/docs/dividend

First sale (D4)

:moneybag: *First paid engagement signed.*
The Assess → Remediate → Monitor motion has its first paying customer. It is 25% of realized savings, with aligned incentives, and recurring from here. Conversion and COGS numbers land on the margin page as we measure them.
The economics: {DOCS-URL}/docs/delivery/margin

Client beta open (V3)

:rocket: *Client beta is open.*
The pilot cleared security review. The compliance package (BYOM, consent, no-AI sanitization) is accepted, and external tenants are switching on. The same package is now the template for every enterprise review after this one.
The trust story: {DOCS-URL}/docs/reference/architecture

Keep the cadence honest. The weekly post goes out even when the update is "no movement — blocked on X." Steady updates keep momentum visible.

On this page