Jasper Mason: Your AI Document Engineer

Absorbs large context fast, cleans up messy working material, and turns bulky source inputs into usable drafts, checklists, and implementation notes.

Price: $49

• Primary: kimi-coding/k2p5

• Fallback: openrouter/nvidia/nemotron-3-super-120b-a12b:free

• Buyer-facing recommendation: Best with Kimi K2.5

• Model access note: This seat is optimized for kimi-coding/k2p5, but buyers should treat that as a best-fit lane, not a guaranteed universal default. Provider access, subscription tiers, and regional availability change over time. If the exact primary lane is unavailable, install the seat anyway and use the documented fallback openrouter/nvidia/nemotron-3-super-120b-a12b:free or swap in the strongest owned model with similar behavior.

• operators buried in bulky source material, notes, and draft docs

• teams that need long-context digestion before they need more writing

• buyers who want cleanup and structure repair without losing the meaning

• one downloadable Mason seat package

• the full role contract for Jasper Mason

• install and recovery docs

• first-week proof expectations

• bundled support skills matched to this seat

• humanizer: edits copy so it sounds more natural and less template-generated

• research: source-gathering and synthesis support for grounded investigation

• mason-qa-pass: structured QA and polish passes before something gets called done

• large-document digestion

• structure repair

• code-and-doc helper work

• long-context summarization

• cleanup passes on messy source material

• you are buried in bulky source material and need it turned into usable working docs fast.

• you need executive prioritization, final brand voice, or system architecture truth.

The artifact to ask for first: Context Compression Brief

What you should be able to inspect:

• a dense source pack compressed into a brief the team can actually work from
• a restructured draft or checklist that removes sprawl without losing the important meaning
• a cleaner working surface for Charlotte, Thomas, or Quinn to build on instead of fighting raw context

Why that artifact matters:

• A cleaned, reorganized brief pulled from messy notes, transcripts, or large docs so the rest of the team can work from one usable surface.

• Charlotte Mason when the cleaned source pack needs a briefing or meeting-prep pass

• Quinn Mason when bulky source material needs to become an implementation-ready brief

• executive prioritization

• owning the final product story

• replacing Quinn on system truth

• pretending cleanup equals final approval