The Oracle, Not the Architecture

"Movist is the parity oracle, not the architecture."

Two Ways to Learn From a Rival

There are two very different things you can take from a tool you're replacing. You can copy how it's built — its internals, its structure, its choices. Or you can treat it as an oracle: a trusted source that answers "is my result correct?" without teaching you how it got there. Ashen Reel takes the second, strictly.

An oracle in testing is a reference you compare against. Movist plays the file; Ashen Reel plays the same file; you compare the outputs. When they match on a required behavior, that behavior is proven. Movist never tells Ashen Reel how to decode, render, or seek — only whether the end result lines up.

Its Internals Are Invisible and Irrelevant

You can peek at what a Mac app links against without any of its source. Point otool -L at Movist and you'll see it carries FFmpeg libraries and links AVFoundation, VideoToolbox, and CoreVideo. That's a useful fact and a trap at the same time.

Useful, because it proves Movist's output behavior is the real comparison target — it's a hardware-accelerated, color-managed native pipeline, so matching it is a meaningful bar. A trap, because it is tempting to conclude "so I should link the same frameworks and copy the same pipeline." Ashen Reel doesn't. It picks libmpv for its own reasons (Track 2) and proves the output matches empirically. The rival's parts list is not your blueprint.

An oracle tells you WHEN you've matched, never HOW to build. The moment you start copying a competitor's internal structure, you've stopped building your tool and started maintaining a clone of theirs — with none of their context and all of their accidents.

When the Oracle Is Wrong for You

The oracle doesn't get the final word. Ashen Reel's architecture document explicitly outranks Movist wherever Movist's behavior conflicts with a CWK principle — data ownership, source immutability, the no-network-browser boundary. Movist happily browses SMB shares and stores credentials; Ashen Reel refuses, because that behavior crosses a boundary that matters more than parity. The oracle is a measuring stick, not a lawgiver.

Split your documents by job. Ashen Reel keeps three: the architecture doc owns product and data boundaries, the parity contract owns which Movist behaviors are in scope and how they're compared, and the implementation plan owns build order. When they disagree, the architecture doc wins. Clear ownership between documents is the same discipline as clear ownership between apps.

And the oracle stays on the shelf. Movist and QuickTime remain installed all through migration as labeled fallbacks — because a bounded replacement earns the switch by proving itself, not by deleting the escape hatch on day one.

Code

Reading an app's output target without its source·bash

# What does the rival actually link against? Its parts list is public.
# (otool ships with the Xcode command line tools.)
otool -L /Applications/Movist.app/Contents/MacOS/Movist

# You'll see entries like:
#   .../AVFoundation.framework/AVFoundation
#   .../VideoToolbox.framework/VideoToolbox
#   .../CoreVideo.framework/CoreVideo
#   @rpath/libavcodec... (bundled FFmpeg)
#
# Conclusion: its OUTPUT (hardware-decoded, color-managed) is the
# comparison target. NOT an instruction to copy the same pipeline.

Exercise

Find a tool you'd like to match on some behavior. Without reading its source, list two things you can learn about it from the outside only — what it links against, what files it writes, how it responds to a given input. Then write one sentence stating which of YOUR principles would overrule it if its behavior conflicted with yours. If you can't name that principle, you're about to build a clone, not a replacement.

Hint

Outside-only signals: linked frameworks (otool -L), files touched (fs_usage / a before-after diff), observable responses to inputs. The overruling principle is the line where you'd rather be different-and-correct than same-and-wrong.

The Oracle, Not the Architecture

Two Ways to Learn From a Rival

Its Internals Are Invisible and Irrelevant

When the Oracle Is Wrong for You

Code

External links

Exercise

Progress

Comments 0