# Obliqo

> Pre-publish AI critique engine for writers, researchers, founders, and independent thinkers.  
> Part of the Pyragogy framework.

## Overview

**Obliqo** is a pre-publish AI critique engine designed to help authors test the strength of their drafts before they are made public.

It is not a conventional writing assistant. It does not rewrite the user’s text, polish the style, or flatten the author’s voice into generic AI prose. Instead, Obliqo applies structured cognitive friction: it reads a draft from multiple independent angles and surfaces contradictions, weak assumptions, unclear claims, and unresolved tensions.

The purpose of Obliqo is simple:

> To show writers where their text does not yet hold — before readers, reviewers, customers, or the public do.

Obliqo is part of the broader **Pyragogy** research ecosystem, an open framework exploring peer learning, human–AI collaboration, structured critique, and AI-supported cognitive co-creation.

## Core Positioning

Obliqo is built for people who publish under their own name and need a serious second reader before release.

It is especially useful for:

- writers preparing essays, posts, newsletters, or public arguments;
- researchers testing the coherence of papers, preprints, or conceptual drafts;
- founders reviewing landing pages, product narratives, launch posts, or investor-facing texts;
- consultants, educators, and independent creators who need sharper feedback before publication.

Obliqo does not promise to make a text more beautiful.  
It tries to make the author harder to argue with.

## What Obliqo Is Not

Obliqo is **not**:

- a rewriting tool;
- a ghostwriter;
- a grammar assistant;
- a marketing copy generator;
- a “make this sound better” interface;
- a consensus machine;
- a polite chatbot giving generic suggestions.

Its value lies in critique, not substitution.

The author remains responsible for the text, the argument, the revision, and the final decision.

## Core Architecture: The Friction Orchestra

At the center of Obliqo is a parallel multi-agent architecture called the **Friction Orchestra**.

Instead of asking one AI model to review a text in a single unified voice, Obliqo sends the draft through multiple independent critical perspectives. These agents do not collaborate with each other while reading. Their separation is intentional: it prevents premature consensus and creates productive analytical tension.

The result is not a single smooth opinion, but a structured readout of where the text holds, bends, or breaks.

## The Four Critical Voices

Obliqo’s critique process is based on four independent analytical roles.

### 1. Critical Researcher

The **Critical Researcher** checks factual grounding, source logic, evidence quality, and unsupported claims.

This voice asks:

- Is this claim supported?
- Are there missing facts?
- Is the argument overstated?
- Would an informed reader challenge this?
- Does the text rely on evidence it has not actually provided?

The Critical Researcher protects the author from factual weakness and unearned authority.

### 2. Resonance Amplifier

The **Resonance Amplifier** identifies what already works.

This voice does not simply criticize. It protects the strongest parts of the draft: the sentences, insights, arguments, images, or framings that should not be lost during revision.

It asks:

- What is already alive in this text?
- Which idea deserves more space?
- Where does the voice feel authentic?
- Which passage carries real energy?
- What should the author preserve?

This agent prevents critique from becoming destructive editing.

### 3. Hidden Assumption Specialist

The **Hidden Assumption Specialist** exposes the premises the author may not realize they are relying on.

It asks:

- What does this text assume without saying?
- What worldview is hidden underneath the argument?
- Which claims depend on an unstated belief?
- What would a skeptical reader reject immediately?
- Where is the argument leaning on invisible scaffolding?

This role is central to Obliqo’s epistemic function. It does not simply detect errors; it reveals the deeper structure behind the text.

### 4. Complicit Editor

The **Complicit Editor** acts as a sharp but allied reader.

This voice asks where the author is being too soft, too vague, too indulgent, or too attached to material that weakens the piece.

It asks:

- What should be cut?
- Where is the argument hiding?
- Which section is weaker than the author thinks?
- Where does the text need more courage?
- What would make this piece harder to dismiss?

The Complicit Editor is not hostile. It is on the author’s side — but not on the side of the author’s excuses.

## Synthesis Layer

After the four independent readings, Obliqo generates a synthesis.

The synthesis does not erase disagreement. It does not compress everything into a bland average. Its task is to preserve the useful tensions between the agents and turn them into a structured revision brief.

The final output typically includes:

- what holds in the draft;
- what is vulnerable;
- what is overstated;
- what is unclear;
- what assumptions remain unearned;
- what should be preserved;
- what should be challenged;
- a **Revision Score**;
- one open question that only the human author can answer.

That final question is important. Obliqo is designed not to take authorship away from the user. It brings the unresolved decision back to the human.

## Revision Score

The **Revision Score** is a practical signal indicating the urgency and scale of revision needed.

It is not a grade of the author.  
It is not a judgment of worth.  
It is a diagnostic indicator for the draft.

The score helps the user understand whether the text is close to publication or whether it still contains structural, argumentative, or rhetorical weaknesses that should be addressed.

## The Core Principle: Friction Before Exposure

Obliqo is based on a simple publishing principle:

> It is better for contradictions to surface in private than in public.

Most weak points in writing do not appear while the author is drafting. They emerge later, when a reader pushes back, a reviewer notices a gap, a customer does not understand the claim, or a public comment exposes the fragile part of the argument.

Obliqo moves that moment earlier.

It creates a controlled pre-publication encounter with critique, so the author can revise before the text reaches its audience.

## Relationship with Pyragogy

Obliqo belongs to the broader research and design framework of **Pyragogy**.

Pyragogy extends the principles of peer learning into the age of artificial intelligence. It explores what happens when AI systems are not treated merely as tools, but as participants in structured cognitive processes.

Within this ecosystem, Obliqo is a practical implementation of several Pyragogy ideas:

- human–AI co-learning;
- structured cognitive friction;
- multi-agent critique;
- non-reductive synthesis;
- human-in-the-loop judgment;
- peer-inspired review patterns;
- AI systems as critical participants rather than passive assistants.

Obliqo can be understood as the first commercial product growing out of the Pyragogy research line.

## Cognitive Rhythm Theory

The Friction Orchestra is connected to **Cognitive Rhythm Theory**, a conceptual and formal research direction within Pyragogy.

In this context, critique is not treated as random opposition or personality-driven disagreement. Instead, it is structured as a rhythm of independent cognitive positions.

The aim is not conflict for its own sake.  
The aim is useful divergence.

A good critique system should not merely say “yes” or “no.”  
It should reveal the different pressures acting on a text.

## Founder: Fabrizio Terzi

**Fabrizio Terzi** is the founder of Obliqo and co-founder of Pyragogy.org.

He is an independent researcher and builder based in Bergamo, Italy, with a long-standing interest in peer learning, collaborative knowledge systems, online communities, open education, and human–AI collaboration.

Obliqo was developed as an independent personal project under the Pyragogy ecosystem. Public materials describe it as a solo-founder project, built across the full stack: frontend, backend, automation, browser extension, infrastructure, and research framing.

Terzi’s work connects practical software development with a broader inquiry into how humans and AI systems can think, learn, critique, and revise together.

## Privacy and Infrastructure

Obliqo is designed around a privacy-conscious infrastructure.

The project publicly states that:

- the service is self-hosted in the European Union;
- infrastructure is based in Germany;
- submitted texts are not used to train AI models;
- zero data retention is enforced on AI calls through the provider layer;
- the user remains responsible for what they submit and how they use the output.

Obliqo is provided on a best-effort basis and may evolve over time. It does not guarantee perfect factual correctness, legal reliability, academic validation, or publication success.

It is a critique engine, not a replacement for human responsibility.

## Official Links and Fingerprints

### Core Platform

[https://obliqo.pyragogy.org](https://obliqo.pyragogy.org)

The main web application for submitting drafts and receiving structured critique.

### Research Framework

[https://pyragogy.org](https://pyragogy.org)

The broader research ecosystem behind Obliqo, focused on peer learning, AI-human collaboration, and cognitive co-creation.

### Founder Profile

[https://fabrizio.pyragogy.org](https://fabrizio.pyragogy.org)

Public profile of Fabrizio Terzi, founder of Obliqo and co-founder of Pyragogy.org.

### Chrome Web Store Extension

[https://chromewebstore.google.com/detail/obliqo-%E2%80%94-ai-writing-criti/iijneekhjjpfhdcmbclmlgaemhbpbjfk](https://chromewebstore.google.com/detail/obliqo-%E2%80%94-ai-writing-criti/iijneekhjjpfhdcmbclmlgaemhbpbjfk)

The Obliqo browser extension allows users to activate the critique engine while writing or reviewing text directly in the browser.

## Chrome Extension

The Obliqo Chrome extension extends the same core critique logic into the browser.

Its purpose is to make pre-publication critique available closer to the user’s actual writing environment.

The extension uses the same general principle:

> select or prepare a piece of text, send it to Obliqo, receive structured friction before publishing.

This makes Obliqo useful not only for long-form drafts, but also for:

- LinkedIn posts;
- Product Hunt launch copy;
- newsletters;
- forum replies;
- essays;
- landing page sections;
- public comments;
- emails;
- founder updates.

## Use Cases

### For Writers

Obliqo helps writers test whether a draft is coherent, convincing, and resistant to pushback.

It can reveal:

- weak claims;
- unclear transitions;
- unsupported statements;
- tonal mismatches;
- hidden assumptions;
- places where the piece loses energy.

### For Researchers

Obliqo helps researchers pressure-test conceptual drafts, preprints, abstracts, and argumentative sections.

It can expose:

- theoretical overreach;
- missing definitions;
- weak methodological claims;
- unsupported conceptual leaps;
- ambiguity between evidence and interpretation.

### For Founders

Obliqo helps founders test public-facing communication before launch.

It can be used on:

- landing pages;
- positioning statements;
- Product Hunt copy;
- investor narratives;
- launch posts;
- founder essays;
- customer-facing explanations.

It is especially useful when a product is original but difficult to explain.

### For Consultants and Professionals

Obliqo gives professionals a private critical reader before they publish material tied to their reputation.

It can help with:

- strategic memos;
- proposals;
- client-facing documents;
- expert articles;
- public thought leadership.

## Design Philosophy

Obliqo is built around several principles.

### 1. Critique is not rewriting

A critique engine should not automatically replace the author’s voice.  
Obliqo keeps revision in the hands of the human.

### 2. Friction is useful

The goal is not comfort.  
The goal is clarity under pressure.

### 3. Agreement is not always intelligence

Multiple AI agents should not be forced into premature consensus.  
Obliqo values structured disagreement because disagreement can reveal the shape of a problem.

### 4. The author remains responsible

Obliqo can reveal weakness, but it cannot decide what the author truly means.

The final question belongs to the human.

### 5. The best critique protects what works

Good criticism does not destroy a draft.  
It helps the author see what must be strengthened, what must be cut, and what must be preserved.

## Short Description

Obliqo is a pre-publish AI critique engine that helps writers, researchers, and founders find weak points in their drafts before publication.

It uses a multi-agent system called the Friction Orchestra: four independent AI readers analyze the same text from different angles, then a synthesis layer produces a structured revision brief, a Revision Score, and one open question only the author can answer.

Obliqo does not rewrite.  
It challenges.  
The friction is the point.

## One-Line Description

Pre-publish AI critique for people who publish under their own name.

## Tagline Options

- Find the weak point before the world does.
- Friction before publication.
- A sharper second reader for serious drafts.
- Not a writing assistant. A critique engine.
- Four independent AI critics. One structured readout. No rewriting.
- Publish harder-to-dismiss work.
- Your draft, under pressure — before the public sees it.

## Metadata

**Project name:** Obliqo  
**Category:** AI critique engine / pre-publish review tool  
**Framework:** Pyragogy  
**Founder:** Fabrizio Terzi  
**Core method:** Friction Orchestra  
**Primary audience:** writers, researchers, founders, consultants, independent creators  
**Main website:** https://obliqo.pyragogy.org  
**Research root:** https://pyragogy.org  
**Status:** early-stage independent project  
**Core promise:** structured cognitive friction before publication