01
Why
Which requirement and tradeoff justify the decision?
Exposes unsupported choices and accidental complexity.
Salesforce Enhanced Chat + Omni-Channel
Find the gaps before the build does.
A critic-only design review system for Salesforce solution architects. It turns an architecture draft into specific, evidence-anchored feedback— then hands the work back to the author.
≤ 5priority findings
4review lenses
2human checkpoints
0rewrites or approvals
Built from practice
The hard part isn’t drawing the happy path. It’s making every decision reviewable.
I’m a Salesforce Solution Architect. I built this editor around a problem I see in real design work: a document can sound complete while leaving builders to invent routing precedence, failure behavior, data ownership, and proof.
This workflow surfaces those gaps early without ghostwriting the design or borrowing the authority of a human architect. The result is stronger thinking, clearer handoffs, and an audit trail that survives the review.
The review method
Why → Flow → Failure → Proof
Four questions keep the critique concrete, traceable, and useful to the person who must revise the design.
02
Flow
Can a builder follow every actor, handoff, and state change?
Turns vague intent into a path a delivery team can trace.
03
Failure
What happens when routing, staffing, or integrations fail?
Pulls the unhappy path into the design before production does.
04
Proof
Which event, field, log, test, or metric proves success?
Makes outcomes testable instead of merely plausible.
The complete loop
From submitted draft to accountable judgment.
Chat is the front door. The repository supplies the routing, record, and human boundaries behind it.
- 01
Submit
Attach the SDD, requirements, assumptions, and diagrams in chat.
- 02
Critique
Receive at most five evidence-anchored findings, ranked by risk.
- 03
Revise
The author resolves, partially resolves, or disagrees—with reasoning.
- 04
Re-review
Resolved issues are acknowledged; remaining gaps are re-anchored.
- 05
Decide
A focused packet moves forward for accountable human judgment.
Readiness is not approval. The editor can prepare a design for formal review. Only an accountable human can approve it.
Evidence, not promises
Inspect the work—not just the claim.
Every demonstration is fictional, reproducible, and preserved in the public repository.
Complete feedback loop
Northstar: from flawed draft to formal-review readiness.
Five preserved artifacts show the draft, specific critique, pre-authored response, revised SDD, and convergent second review.
Draft→Critique→Revision→Ready
Open the five-artifact cycle Unseen evaluationMorrow Peak: a distinct design, reviewed in isolation.
A fresh model run received the portable editor and an unseen SDD—without a golden answer or pre-authored findings.
Inspect the recorded run Portable engineFive files. One job each.
Identity, rules, examples, references, and instructions form a reusable critique engine that can run independently.
Explore the editor folderThe operating contract
Critique, don’t create.
The editor does
- Quote the exact passage that fails
- Explain the downstream consequence
- Return a focused task to the author
- Route judgment calls to a human
The editor never
- Writes replacement design content
- Invents missing requirements or details
- Generates diagrams for the author
- Claims architecture approval
Open the system
Make the design easier to build, test, operate, and defend.
Review the complete workflow, run the fictional demo, or lift the portable editor into a Claude Project.