Media operations diagnosis

Before you buy more storage,map the operation.

Most media teams do not have a storage problem. They have five undocumented handoffs, two people who know where things are, and no defined end state for a finished project. The Blueprint finds which one is actually costing you, and what to do about it in the next 90 days.

Start your $499 Blueprint → Read a full Blueprint ↓

One roughly 90-minute working audit. Written Blueprint within five business days. No footage upload, no credentials, no software commitment.

Media operation / current state Select a stage

OwnerWhoever pulled the card

RecordedTrigger, destination, naming rule, and who decides

QuestionDoes the same shoot land in the same place twice?

Seven stages are mapped in the session. These four are where the cost usually sits.

$499Fixed price

~90 minWorking audit

5 daysWritten delivery

100%Credited to an ensuing build when terms permit

Start here

You already know something is wrong. This narrows it down.

Eight things we hear in almost every intake call. Check the ones that are true this month.

A finished project exists on more than one drive and nobody is certain which one is current. Finding a shot from two years ago means asking one specific person. Someone has re-shot or re-cut something the team already had. Working storage is past 80% and the plan is to buy more. A client has opened an expired review link, or approved the wrong cut. How a card gets named depends on who offloaded it that day. Nobody has restored a file from the archive in the last twelve months. One person knows where everything lives, and they are also the busiest.

This is a conversation starter, not the deliverable. The Blueprint ranks findings against your actual evidence, not a checklist.

The deliverable

This is the whole thing. Read it before you buy it.

A finished Blueprint for a 22-person branded-content studio deciding whether to buy a media asset manager. Eight sections, every claim marked by how it is known, and a recommendation to buy nothing. Same structure and same depth as the one you would receive.

northbeam-studios · media-operations-blueprint · v1 Evidence cutoff 14 Mar · 8 sections

Delivered as PDF and markdown. Yours is written against your operation, your decision, and your constraints.

Section 01

Executive answer

Decision this Blueprint supports: Should we license a media asset manager this quarter, or expand the shared storage array first?

Neither, first. The evidence does not support a cataloguing purchase or a capacity purchase as the next move. Both would sit on top of the actual constraint rather than remove it.

Northbeam has no defined end state for a finished project. Each editor decides independently when a job is done, what gets kept, and where it lands. That single missing definition produces four of the five ranked findings below: the duplicate masters, the 88% array, the retrieval dependency on one producer, and the untested LTO set. A MAM introduced now would index an inconsistent library and reproduce the inconsistency in search results.

Recommended next move: define and enforce a project close-out — one naming and identifier convention, one archive destination per project type, one checklist that must pass before a job is marked complete. Run it manually on the next three projects before automating any part of it. Re-evaluate a MAM at day 90 against a library that has a shape.

Most important uncertainty: the 2019–2022 LTO set has not been restored from since it was written. Recoverability was not tested in this engagement and cannot be assumed. A single restore test is the cheapest high-value action available to the team and is scheduled first in the roadmap.

Not recommended right now

Storage expansion (~$14k quoted). The array is at 88% because completed work never leaves it. Roughly 40% of current occupancy is finished projects with no reason to stay on working storage. Capacity is a symptom here, not the constraint.

Scope and evidence

Primary operation mapped	Branded-content delivery, from card offload through client delivery and archive. One team, 22 people.
Session participants	Owner/EP, senior producer, lead editor, freelance AC (partial).
Evidence supplied	Completed intake, one roughly 90-minute working audit, screen-share of the array's folder structure, a sanitized storage diagram, one anonymized delivery thread.
Not inspected	LTO restore behaviour, Frame.io retention settings, the 2019–2022 offsite copies, any client-side storage, hardware health, network throughput.
Constraints named by the team	No per-seat subscription above $40/user/mo. No workflow change during the Q2 campaign block. The array stays where it is. No new full-time headcount.
Evidence cutoff	14 March. Nothing after this date is reflected.

Section 02

Current-state map

How media actually moves today, with every claim marked by how we know it.

Observed Directly visible in supplied material.
Stated Described by the team, not independently tested.
Inferred Reasoned from the above; the reasoning is given.
Unknown Important and not established here.

Stage	Owner	System	Trigger → output	Friction	Evidence
Ingest	Shooter or AC	Laptop → shuttle SSD → array	Card pulled → folder on `/Volumes/NB-WORK`	Three naming patterns in use. Verification is by eye.	Observed
Active work	Assigned editor	Premiere on the array	Project created → cut, versions, exports	Versions live beside the project with no scheme. Nine `_FINAL` variants on one job.	Observed
Review	Producer	Frame.io, expiring links	Export → link → client notes	Approvals live in email threads and are not attached to a version.	Stated
Delivery	Producer	WeTransfer or client portal	Approval → master out	Delivered masters are not recorded anywhere the team can query later.	Observed
Archive	Unassigned	LTO-7, occasional; array otherwise	No trigger. Happens when space runs out.	No definition of done. Completed work stays on working storage indefinitely.	Observed
Retrieval	One senior producer	Memory, then Finder search	Request → a person goes looking	Median time to locate an older asset was described as “an afternoon.”	Stated
Reuse	—	—	Rarely attempted	Reuse is not attempted because retrieval is not trusted, not because the library is thin.	Inferred

Boundary note: this map covers one team and one recurring workflow. Freelance edit-at-home cycles were described but not mapped, and are carried as an unknown in section 08.

Section 03

Priority bottlenecks and unknowns

Ranked by operational consequence and relevance to the decision — not by what is easiest to sell you.

01Observed

No defined end state for a finished project.

Close-out is decided per editor per job. Three duplicate masters were found across two volumes during the session, and finished work is the largest occupant of working storage.

Consequence
Drives findings 02, 03 and 04. Blocks any catalogue from being trustworthy.

Confidence
High

First proof
Write the close-out checklist; run it manually on the next three projects.
02Unknown

The 2019–2022 LTO set has never been restored from.

Roughly 60TB of archive-only material. Tapes were written on a drive that is no longer in the building. Recoverability was not tested in this engagement.

Consequence
Potential total loss of three years of finished work, currently unquantified.

Confidence
Unknown by definition — that is the finding.

First proof
Restore two tapes chosen at random. One afternoon, no purchase required.
03Stated

Retrieval depends on one producer's memory.

Older assets are found by asking the same person, who is also carrying the heaviest project load. No index exists that survives their absence.

Consequence
Reuse effectively stops when they are out; estimated at several hours per week of avoidable search.

Confidence
Medium — consistent across three accounts, not measured.

First proof
Log every retrieval request and its duration for two weeks.
04Observed

Working storage is at 88% and rising ~2% per month.

An expansion quote is already in hand. Approximately 40% of occupancy is completed work with no operational reason to remain.

Consequence
A capacity purchase now buys roughly eleven months and preserves the underlying behaviour.

Confidence
High

First proof
Archive the three oldest completed projects under the new close-out rule and measure what is recovered.
05Inferred

Approvals are not attached to the version they approved.

Sign-off lives in email while versions live on the array under ad-hoc names. Two of the described re-cuts are consistent with a client approving a superseded version.

Consequence
Occasional re-work at the most expensive point in the schedule.

Confidence
Medium — the pattern fits; specific incidents were not reconstructed.

First proof
Adopt a version identifier that appears in the filename, the review link, and the approval reply.

Section 04

Findings by operating layer

The same operation read through each layer separately, so a fix in one is not mistaken for a fix in another.

Layer 01

Storage and protection

Observed

One 120TB array serves as working storage and, by default, as the archive. LTO-7 exists but is written occasionally and without a trigger. Copies are not tracked, and no document states how many copies of a finished project should exist or where they should live.

Two fault domains were described: the array itself, and the tape set. They are in the same building. Whether the 2019–2022 tapes are readable is unknown — see finding 02.

Not claimed: no hardware health check, throughput test, backup-recoverability test, or capacity forecast beyond the team's own stated growth rate was performed.

Layer 02

Organization, metadata, and retrieval

Observed

Three naming conventions are in active use, corresponding roughly to who joined the team when. Project folders carry a client name and a loose date; there is no stable identifier that survives from ingest to delivery to archive.

Metadata beyond the filename does not persist past the edit. Nothing that a person knows about a shot — the client, the campaign, whether it cleared legal — is written anywhere a search could reach.

Retrieval today is a person, not a system. That works at the current library size and stops working at the next one.

Layer 03

Ingest, handoffs, review, and delivery

Stated

Each stage functions. The failures are at the seams. Offload has no verification step beyond visual inspection, so a bad copy would not be noticed until the footage was needed. Responsibility for a project between picture-lock and delivery is not assigned to anyone by name.

Review links expire on a default the team did not choose. Approvals return by email and are not bound to the version they approved, which is the mechanism behind finding 05.

Delivered masters leave the building with no record the team can query afterwards. Asked what was delivered to a client in 2024, the operation's honest answer is to go looking.

Layer 04

Automation and AI fit

Inferred

No automation is currently justified. Automating a process with three naming conventions and no defined close-out would encode the inconsistency rather than remove it, and would make it harder to change later.

Two bounded opportunities exist once close-out is real, in this order:

Checksum verification at offload. Deterministic, cheap, no model involved. Removes an unmeasured risk at the earliest point in the chain.
Automatic index entry on close-out. Writing the project ID, client, date, and destination to the index when a job is closed, rather than asking a person to remember.

Content-level AI — transcript search, visual tagging, automatic selects — is a day-90-or-later question. It requires a consistent library to be useful and a human review step to be trustworthy. No accuracy claim is made here.

Layer 05

Ownership and continuity

Stated

No one owns the archive. It is the only stage in the map with an unassigned owner, and it is the stage where every unresolved finding accumulates.

Operational knowledge is concentrated in one senior producer: where older work lives, which tape holds what, which client wanted which deliverable format. None of it is written down. This is a single point of failure with no redundancy and no documentation, and it is the finding most likely to become urgent without warning.

Note: this is an organizational finding, not a technical one. No purchase resolves it. A named owner and a written index do.

Section 05

Recommended target state

One coherent direction, justified by the evidence above. Architecture direction, not an implementation specification.

The shape Northbeam needs is not a new platform. It is a boundary between working storage and the archive, with one identifier that survives the crossing, and one named owner for the crossing itself.

[source / ingest] → [controlled working path] → [archive / index]
                                    → [search / review / reuse]
                                              ↕
                              [ownership, evidence, maintenance]

Read left to right, the change is small: one gate between the working path and the archive. Read bottom to top, it is the whole point — every stage above depends on someone owning it and on the evidence being written down as work happens rather than reconstructed later.

Keep / change / pilot / defer

Decision	Item	Rationale	Proof required
Keep	The array as working storage	Correctly sized for active work once finished work stops living on it.	None. Already evidenced.
Keep	Premiere and the edit workflow	No finding traces to the edit environment.	None.
Keep	Frame.io for client review	The tool is not the problem; the link and approval discipline around it is.	None.
Keep	LTO as the archive medium	Appropriate for this volume and budget posture — conditional on the restore test.	Two random tapes restore successfully.
Change	Project identifier at ingest	One ID, assigned once, carried to delivery and archive. Prerequisite for every other change.	Applied cleanly to three consecutive new projects.
Change	Close-out checklist gates “complete”	Removes the missing definition that drives four of five findings.	Three projects closed under it without exception.
Change	Archive destination by rule	One destination per project type, chosen by rule rather than by whoever is closing the job.	Rule written; no ad-hoc destination in 30 days.
Change	Approvals bound to a version	Version ID appears in filename, review link, and approval reply.	One full project cycle with no ambiguity about what was approved.
Change	Named archive owner	The only stage with no owner is the stage where findings accumulate.	Named in writing, with the close-out step in their remit.
Pilot	A plain archive index	Project ID, date, client, tape, one line of contents. A spreadsheet is sufficient to prove the behaviour.	Maintained without prompting for 60 days.
Pilot	Checksum verification at offload	Closes an unmeasured risk at the cheapest point. No model, no subscription.	Runs on every offload for 30 days without slowing the AC down.
Defer	Media asset manager	Would index an inconsistent library. Re-decide at day 90 against real retrieval data.	Index maintained + 60 days of retrieval logs.
Defer	Storage expansion (~$14k)	Capacity is a symptom of the missing close-out, not an independent constraint.	Real growth rate measured after close-out reclaims space.
Defer	Automatic tagging / AI search	Requires a consistent library first; accuracy is unevidenced at this stage.	Consistent library + a defined human review step.
Defer	Any custom build	No evidence yet that this operation needs software written for it.	A constraint that survives days 0–90 and has no off-the-shelf answer.

Why an index and not a catalogue

A spreadsheet with a project ID and one line of contents answers the retrieval question actually being asked, costs nothing, and produces the consistency a real catalogue would need later. If it is being maintained at day 90 and still not sufficient, that is genuine evidence for a MAM purchase. If it is not being maintained, a MAM would not have been either.

Section 06

90-day roadmap

Sequenced so each step produces the evidence the next one needs. Every line has an owner, a dependency, and a condition that says it is finished.

Horizon	Action	Owner	Dependency	Done when
Now0–30 days	Restore two tapes chosen at random	Lead editor	Locate a compatible LTO-7 drive	Both restore and play, or the failure is documented
	Write the close-out checklist	Owner/EP	None	One page exists and the team has read it
	Adopt the project identifier on new jobs	Senior producer	Close-out checklist drafted	Three consecutive new projects carry it
	Log every retrieval request and its duration	Senior producer	None	Two continuous weeks of entries
Next31–60 days	Run close-out manually on three projects	Lead editor	Checklist written	Three closed with exceptions recorded
	Archive the three oldest completed jobs	Archive owner	Restore test passed; destination rule written	Array space recovered is measured against the $14k quote
	Start the archive index	Archive owner	Project identifier in use	Every job closed since day 30 has a row
	Bind approvals to versions	Senior producer	Version ID convention agreed	One full project cycle with no version ambiguity
Later61–90 days	Assign archive ownership in writing	Owner/EP	Close-out proven manually	Named in a role description, not volunteered
	Re-decide the MAM	Owner/EP	Index maintained + retrieval logs	A decision recorded with the evidence behind it
	Re-decide storage expansion	Owner/EP	Space recovered by archiving is known	Growth rate recalculated post-close-out
	Schedule the standing restore test	Archive owner	First restore test complete	On the calendar twice yearly with a named owner

Nothing in this roadmap requires a purchase from Vaultline. If the team executes days 0–60 and the constraint is gone, that is a successful outcome of this Blueprint.

Section 07

Media Nexus scoped

The complete system, with your scope drawn on it — so you can see what you would and would not be buying, and judge the rest of this document against it.

Media Nexus is Vaultline's local-first media operations system. It is built around roles rather than fixed hardware: the same software runs on one machine, on an edit bay plus a server, or against a NAS. Nothing about it assumes a particular storage layout, which is why it can sit on the array and the LTO set Northbeam already owns.

One architectural rule governs the whole system and is the reason it is safe to point at a working operation: the modules never scan storage themselves and never write toward source media. A node reads, indexes, and generates derivatives; every module above re-reads what Archive already indexed. Your masters are never the thing being modified.

System architecture

Read top to bottom, the system only ever moves in one direction: source media is read, an index and a set of derivatives are produced, and every module reasons over the index. Read as a whole, that is the property that makes it appropriate for an operation that cannot afford to be experimented on.

Module catalog, with Northbeam scope

Maturity below is Vaultline's own internal status, reported as it stands rather than as it would sell. Two of these are experimental and one is currently disabled.

Module	What it would do here	Maturity	Northbeam scope
Core	The platform: index, jobs, permissions, and Support — out-of-band diagnostics and recovery that work even when the server is down.	Production-ready	Phase 1
Archive	Answers what media do we have. The index that replaces the spreadsheet once the spreadsheet has proven the behaviour.	Production-ready	Phase 1
Relay	Card offload with verification, and a storage map that proves a copy exists rather than assuming it. Directly addresses the unverified-offload finding in layer 03.	Production-ready	Phase 1
Ops	Surfaces what needs attention — capacity pressure, jobs that failed, work that never reached the archive. The standing answer to finding 04.	Production-ready	Phase 1
Post	Derives editorial state from what Archive already indexed — which cut is live, what is stalled — without anyone maintaining a tracker.	Production-ready	Phase 2
Review	Binds approval to a specific version. This is the mechanism behind finding 05, solved in software rather than by discipline.	Beta	Phase 2
Photo	Stills as a job: pool, cull, numbered selection rounds, edit handoff, finals. Relevant only if Northbeam's stills volume grows.	Beta	Not needed
Delivery	Records what was delivered to whom, so the “what did we send this client in 2024” question has an answer.	Disabled	Later
Automation	Versioned action packs run as bounded, restricted jobs. Where checksum-on-offload and auto-index-on-close-out would live.	Beta	Later
Agent	A conversational layer over the modules, answering with citations rather than becoming a second source of truth.	Experimental	Not scoped
Brand	Tracks which brand materials are current and flags outdated usage. An agency concern, not this operation's.	Experimental	Not scoped

Search and local AI are not modules. They are shared capabilities owned by the module contracts above — which is why there is no separate line item for them, and no separate licence. Tagging and transcription run locally on your hardware; no footage is uploaded anywhere to make them work.

Phased against your roadmap

Phase 1The foundation

CoreArchiveRelayOps

On the existing array. This is the whole of what section 08 calls the Archive Pilot, and the only phase that would be scoped from this Blueprint.

Replaces: the spreadsheet index, manual offload verification, and the capacity surprise.

Phase 2The work in flight

PostReview

Once the foundation has been running long enough to have a library worth reasoning over. Neither is useful before close-out is real.

Replaces: the version ambiguity behind finding 05 and the informal “where is that job” question.

Phase 3Only if earned

DeliveryAutomation

Only against measured demand. Delivery is currently disabled in the product; Automation is beta. Neither should be committed to on the strength of this document.

Replaces: nothing that is hurting today.

What stays exactly as it is

Premiere and the edit workflow. Media Nexus does not touch the NLE. Post reads project files; it does not run the edit.
Your storage. The array and the LTO set are yours, stay where they are, and are read rather than migrated.
Client review, if you want it that way. Frame.io can remain; Review is an option, not a requirement of the foundation.
The close-out decision. No software decides what “finished” means for your operation. The system enforces the definition; it does not supply it.
The archive owner. A person, not a feature. Every finding in layer 05 survives any software purchase.

Our recommendation on Media Nexus, for this operation, today

Not yet, and possibly not at all. Everything in Phase 1 above depends on four things Northbeam has not done: a close-out definition that is being followed, a passed restore test, one identifier convention that survives three projects, and a named owner. All four are free. Prove the behaviour with a spreadsheet for 60 days. If the index is being maintained and the team has outgrown it, Phase 1 becomes a real option worth pricing. If it is not being maintained, no software would have been maintained either — and that is a more useful thing to learn for $499 than a licence would have been.

Vaultline builds Media Nexus, so treat this section with the scepticism that deserves. It is specified here in full precisely so the recommendation against buying it can be checked against what is actually on offer. Section 08 sets out every option, including the ones with no Vaultline involvement.

Section 08

Implementation options, unknowns, and non-claims

Four ways forward, including doing nothing. One is recommended; the reasoning is given so you can disagree with it.

Option 01
No project now

Preserve what this Blueprint established and change nothing else. Even taken alone, the team keeps the workflow map, the ranked findings, and the knowledge that the LTO set is untested.

Viable. Not recommended only because the restore test is cheap and the exposure is real.
Option 02
Internal execution
Recommended

Northbeam runs the 90-day roadmap itself. Every action is within the team's existing skills and none require a purchase. Estimated effort is a half-day for the restore test, a few hours to write the close-out checklist, and a standing few minutes per closed project.

Recommended because the constraint is a missing operating decision, not a missing capability. Buying software before making the decision converts a cheap problem into an expensive one. If the roadmap is executed and the constraint is gone at day 90, no further engagement is needed.
Option 03
Media Nexus Archive Pilot

A fixed-scope archive foundation on the team's existing hardware, covering the scope set out in section 07.

Not available yet. All four prerequisites in section 07 are unresolved. Revisit at day 90 if the index is being maintained and has been outgrown.
Option 04
Bespoke Media Operations Build

Custom workflow, integration, or hardware implementation under a new written scope.

Not justified. Nothing in the evidence indicates this operation needs software written for it. Revisit only if a constraint survives the full 90 days and has no off-the-shelf answer.

Unknowns carried forward

Whether the 2019–2022 LTO set is readable. Untested. Resolved by the day-30 restore test.
The true retrieval cost. Described as “an afternoon” but never measured. Resolved by the two-week log.
Frame.io retention settings and what happens to review assets over time. Not inspected.
Whether offsite copies of the 2019–2022 material exist. Stated as “probably,” not confirmed.
Freelance edit-at-home cycles. Described but outside the mapped boundary.
Real storage growth rate once completed work stops accumulating on the array.

Non-claims

No hardware health, backup recoverability, security, or compliance claim is made anywhere in this document unless specifically evidenced above.
No AI accuracy claim and no cost-savings figure is asserted.
No files, storage, configurations, or production systems were changed by this Blueprint.
No implementation feasibility is promised. Any build requires a separate written scope.

Clarification window: send one consolidated set of questions within 10 business days of delivery and we answer it in a single pass. New analysis, additional teams or workflows, system access, implementation planning, or hands-on work requires a separate written scope.

Eight sections, at this depth, written against your operation, your decision, and your constraints.

Start your $499 Blueprint →

How it works

Four steps. Every one of them has an edge.

Enough structure to see the whole system, and a hard stop when the package is delivered.

01

Complete the intake.

Twelve written questions: the decision you are making, the shape of the workflow, the friction that costs you something, and the constraints nobody is going to change. About fifteen minutes.
Produces: a scoped session agenda, sent back before we meet
02

Map the operation together.

One roughly 90-minute remote working audit across receipt, active work, review, delivery, archive, retrieval, and reuse. Screen-share of folder structures helps. No credentials, no confidential media, nothing installed.
Produces: the opportunity map in section 02, marked by evidence
03

Receive the written Blueprint.

Within five business days of the session and complete intake. One consolidated round of clarification is included — send everything at once and we answer it in one pass.
Produces: the eight-section document you just read, specific to you
04

Decide, and owe us nothing.

Act on it internally, sit on it, prove a foundation with an Archive Pilot, or use it to scope a build. No follow-on engagement is automatic and there is no retainer at the end of this.
Produces: a decision you can defend to whoever signs for it

If it does point at a build

The Blueprint is the discovery. The build is a separate decision.

Roughly half of these end with the team doing the work themselves. When one does justify a build, the Blueprint is what makes that scope bounded instead of open-ended.

Media Operations Blueprint$499 · diagnosis and roadmap

Where you are. Everyone starts here, including teams who already know they want a build.

Archive Pilot$4,669 · fixed foundation

When existing hardware and one defined archive outcome can prove the foundation before anything larger.

Bespoke Media Operations BuildCustom scope · phased

When the operation genuinely needs custom workflow, integration, or hardware implementation.

When the active order terms permit it, the $499 fee is credited once against a directly ensuing written Archive Pilot or Bespoke Build scope.

Good fit

Teams with real media movement and a decision in front of them.

Production, post, agency, branded-content, or in-house media teams
A recurring workflow across ingest, storage, review, delivery, archive, or search
A near-term infrastructure, workflow, or custom-build decision with money attached
Willingness to name constraints and tell evidence apart from assumption

Not this scope

The Blueprint does not include:

Scanning, recovery, migration, or deduplication
Installation, configuration changes, or custom code
Hardware procurement, training, or recurring support
Open-ended consulting or access to confidential footage

Your starting point

Map the operation before you scope the build.

The Blueprint stands on its own. It is useful if you buy nothing else, and it is the discovery foundation if a build turns out to be the answer.

$499fixed price
one-time

One roughly 90-minute working audit
The complete eight-section package within five business days
One consolidated clarification round
Secure payment handoff; scope confirmed in writing before work begins

Questions

Clear boundaries before you begin.

Is this a sales call?+

No. It is a paid deliverable that frequently recommends doing nothing with Vaultline. The sample you just read ends by telling the client not to buy the thing they were about to buy.

Do you need access to our footage or systems?+

No. We work from structured intake, one remote session, and optional sanitized diagrams or screenshots. Do not send credentials or confidential media.

We already know we need a build. Is this a detour?+

No — it is the discovery that makes the build scope bounded. Without it, a build quote is guesswork priced defensively. The Blueprint is what turns it into a specification.

Does the $499 roll forward?+

When the active order terms permit it, the fee is credited once against a directly ensuing written Archive Pilot or Bespoke Build scope.

What if the fixed scope is not a fit?+

If qualification shows before the session that the Blueprint cannot deliver its promised package, you get a full refund or a separately approved alternative.

How long does the whole thing take on our side?+

Roughly two and a quarter hours total: fifteen minutes of intake, the roughly 90-minute working audit, and a short read. Nothing else is asked of your team.

You already know something is wrong. This narrows it down.

This is the whole thing. Read it before you buy it.

Scope and evidence

No defined end state for a finished project.

The 2019–2022 LTO set has never been restored from.

Retrieval depends on one producer's memory.

Working storage is at 88% and rising ~2% per month.

Approvals are not attached to the version they approved.

Storage and protection

Organization, metadata, and retrieval

Ingest, handoffs, review, and delivery

Automation and AI fit

Ownership and continuity

Keep / change / pilot / defer

System architecture

Module catalog, with Northbeam scope

Phased against your roadmap

What stays exactly as it is

No project now

Internal execution

Media Nexus Archive Pilot

Bespoke Media Operations Build

Unknowns carried forward

Four steps. Every one of them has an edge.

Complete the intake.

Map the operation together.

Receive the written Blueprint.

Decide, and owe us nothing.

The Blueprint is the discovery. The build is a separate decision.

Teams with real media movement and a decision in front of them.

The Blueprint does not include:

Map the operation before you scope the build.

Start with the operation you have.

Clear boundaries before you begin.