Semantic Anatomy

Analysis basis

The entire report is based on the self-reported description provided by the project author. No external verification or historical data is available.

The description states that Semantic Anatomy:

• Transforms an image into a structured visual pipeline.
• Progressively analyzes images through seven stages: spatial regions → objects → relationships → composition/color theory → themes → embedding space → evidence graph and 3D atlas.
• Exports data as JSON, linked notes vaults, and 3D scene packages.
• Uses a canonical Zod contract for validation.
• Supports multiple vision model providers (local Ollama, hosted OpenAI-compatible).
• Includes CI validation via npm run validate.
• Has a provider adapter pattern to support new backends.

Inference The tool appears to be a developer-facing framework or pipeline for structured visual AI analysis, not a consumer product. It is built with Codex, FastAPI, Next.js, React, Three.js, and Python stack.

The author states:

• Semantic Anatomy addresses opacity in image AI by making interpretive claims auditable.
• It turns “captions you can’t audit” into inspectable evidence chains.
• The tool enforces honesty via schema validation — hallucinations are validation errors, not UX surprises.

Claim vs. Fact

These are self-reported positioning statements. No evidence of market traction or adoption is provided.

The description states:

• The primary audience is developers building on vision models.
• It supports CI validation and batch processing for evaluation harnesses.
• It enables collaboration between AI agents and tools via a shared schema.

Inference The ICP appears to be developers or teams working with vision models, particularly those needing structured outputs and auditability. No named customers or use cases are provided.

Not evidenced.

Observation

There is no mention of pricing, monetization, or business model in the description.

The description states:

• Built with Codex, FastAPI, Next.js, React, Three.js, Python, TypeScript.
• Uses GPT-5.6 for reasoning through schema and pipeline logic.
• Local Ollama as fallback; optional hosted OpenAI-compatible provider.
• Zod contract for validation.
• CI validation via npm run validate.
• Provider adapter pattern for backend switching.
• Exports include JSON Schema, 3D atlases, and DCC tool compatibility.

Inference The technical stack suggests a developer tool with strong schema enforcement and modularity. No evidence of production deployment or performance metrics.

Not evidenced.

Observation

The project was built in a hackathon (Build Week), submitted to the OpenAI 2026 hackathon, and has no evidence of revenue, users, or adoption beyond its own description. It is not evident that it has moved past prototype stage.

Not evidenced.

Observation

No mention of competitors or market positioning beyond self-description. The author does not reference similar tools or platforms in the space.

• No traction evidence: The tool is described as a hackathon project with no known users, customers, or revenue.
• Unproven commercial viability: No business model or monetization strategy is presented.
• Self-contained tooling: The project appears to be a developer utility without a clear path to broader adoption or integration.
• High technical dependency on Codex and GPT-5.6: These tools are not publicly available in the same form, raising questions about scalability or replicability.

Inference The lack of any commercial evidence or user feedback raises concerns about whether this will evolve into a viable product or service.

1. What is the actual use case for developers who would adopt this tool?
2. Has there been any internal testing or pilot with real teams using it?
3. How does the schema validation impact performance or latency in real-time applications?
4. Are there plans to open-source or license the core components?
5. Can you demonstrate a working example of the pipeline in action?