I built the private semantic layer without knowing Perplexity was building the public one. That’s not derivative. That’s convergent. Two architectures, same epistemic posture, opposite starting points. This is what I’m bringing to the NYC AI community.

Text below is LLM output with inferential guidance (except this).

The same problem, opposite directions.

Perplexity routes across the world’s knowledge in real time — pulling from the web, selecting sources, synthesizing forward from what the material implies rather than what it confirms. That forward-inference quality, what I’ve been calling its intuitive posture, is largely a routing artifact: Sonar sees ranked, multi-source context shaped by a retrieval decision before it generates a single token.

Vivify routes across your knowledge at corpus time — pulling from felt meaning, selecting inferences by co-occurrence weight and tension score, synthesizing forward from inside the material. The co-occurrence graph is retrieval routing. The tension score identifies which inferences carry the most semantic load for this query. Reify reconstructs from that structure without naming a keyword or citing a source.

The epistemic posture is identical. The data is not.

The architecture that emerges from putting them together.

  • Perplexity — public retrieval layer: case law, research, precedent, public knowledge — routed and synthesized forward in real time
  • Vivify — private semantic layer: the person’s own inferences, tension scores, emergent categories — routed and synthesized forward from the corpus
  • Reify (synthesize mode) — holds both simultaneously, the way it already holds two inferences: not alternating, not summarizing, finding the place where they are the same thought

The output is navigational. Neither layer sees the other’s data. The private corpus never touches Perplexity. The public synthesis never contaminates the private structure.

This is also the Cloudflare architecture: Perplexity as the public coordination layer, a Dynamic Worker as the ephemeral isolate where sensitive material is processed, a Durable Object storing only the vivified structure. The isolate is the privacy boundary. The layers never mix.

The epistemic posture as a prompt property.

Perplexity’s forward-inference quality is not locked to Sonar’s weights. It is a prompt posture — a refusal to retreat to citation, a requirement to build from implication rather than confirmation. The reify prompt already encodes this:

  • Speak from inside the meaning, not about it
  • Do not mention keywords by name — let them shape the prose
  • Do not reference the pipeline, categories, or JSON

Any capable model, given a prompt that removes the retreat option, can hold the Perplexity posture. The worker carries the epistemic posture as its prompt template. Posture travels with the worker spec, not with the model choice.

What I’m bringing to the table.

Not a Perplexity competitor. Not a RAG implementation. A private semantic layer that Perplexity doesn’t have and can’t build — because it requires local-first architecture, a private corpus, and a pipeline that routes through felt meaning rather than web retrieval.

The two layers are complementary by design. Perplexity handles what’s public. Vivify handles what’s private. Reify holds the synthesis. The output serves the person in the conflict, not the system processing them.

That’s the pitch. And it was built before I knew it was one.

Part of the Dimensional Fields project — local-first, privacy-preserving, human-centric.