THE OCTOPUS DATALINK ENGINE

One Idea. Infinite Connections.

Long before “Cloud”, “Big Data” or “AI” became everyday language, the Octopus Datalink was conceived as something deceptively simple:

A digital business partner capable of taking one idea and connecting everything needed to turn it into reality.

Not merely a database.

Not merely an online shop.

Not merely crowdfunding.

Datalink was designed to connect people, products, components, suppliers, manufacturers, retailers, customers, investors, information, pricing, production and distribution into one continuously linked economic system.

And crucially:

It wasn’t merely imagined. It was built.

FROM AN IDEA TO AN ENTIRE BUSINESS

Imagine you have invented a product.

Traditionally, you would have to find your own suppliers, obtain quotations, calculate production costs, find manufacturers, understand minimum production runs, work out retail margins, approach retailers, find investment, organise distribution and somehow determine whether anybody actually wanted the product before spending thousands of pounds producing it.

The Octopus Datalink was designed to connect those isolated problems together.

Enter the product once.

Define what it needs.

And Datalink begins connecting the rest.

Product → Components → Suppliers → Manufacturers → Pricing → Production → Retailers → Customers → Orders → Investment → Distribution

The result was intended to be something much more powerful than a database:

A live economic network in which changing one piece of information could affect everything connected to it.

WHAT COULD DATALINK DO?

Build the Product

A creator could define a product and its constituent components.

Those components could then be connected to suppliers, quantities, prices and alternative sources.

The surviving Microsoft Access prototype demonstrates this directly. The Peter Pan Adventure Boardgame record is connected to individual components, suppliers and associated business information.

Build the Business Around It

The underlying database wasn’t limited to products.

Its relational structure included:

Businesses
Contacts
Addresses
Communications
Links
Media
Products
Components
Suppliers
Customers
Accounts
Price Sets
Orders
Order Details

Information could therefore be associated rather than repeatedly recreated.

The surviving relationship diagrams show a central Content architecture linked through tables for addresses, communications, links, media, pricing and other information.

Connect Everything to Everything Else

At the heart of the architecture sits a particularly important structure:

CNest

Its surviving fields include:

SourceID
ParentID
ChildID
Role
Department
Quantity
Estimate
Selected
Discount Threshold
Discount Rate
Shipping Cost

That is important because Datalink wasn’t merely storing isolated records.

It was designed to describe relationships between records.

A product could contain a component.

A component could connect to a supplier.

A supplier could connect to pricing.

Pricing could change according to quantity.

Those relationships could then affect the economics of the product itself.

It was a chain of live connections — not islands of information.

CHANGE ONE THING — SEE WHAT HAPPENS

This was one of Datalink’s most powerful ideas.

Suppose a creator wanted to manufacture:

1,000 units.

Change that to:

5,000 units.

Different supplier price bands could become applicable.

Component costs could change.

Unit manufacturing cost could change.

Margins could change.

The break-even point could change.

The amount of funding required could change.

The commercial viability of the entire project could therefore change.

Instead of discovering those consequences months later, Datalink was intended to expose them while the creator was making the decision.

ALTERNATIVE CONNECTIONS — BUILT-IN RESILIENCE

A component need not depend upon one supplier.

Different suppliers could be connected to the same requirement.

That meant the system could potentially compare:

Price
Quantity
Availability
Location
Lead time
Terms

If one connection failed, another could replace it.

The objective was not simply automation.

It was economic resilience through interconnected information.

FROM PRODUCT TO MARKET

Once the economics worked, the same system could continue downstream.

Products could be exposed to consumers and retailers.

Potential customers could express demand.

Orders could accumulate.

Performance could be monitored.

Retailers could see evidence of consumer interest before committing themselves.

And production would only proceed when sufficient demand existed.

The contemporary Octopus Initiative documentation expressly describes products carrying their price, minimum target, units sold to date and registration information, with production commencing once sufficient orders had accumulated.

That was the Crowd-Mechanic operating inside a much larger economic architecture:

Participation → Threshold → Outcome

THE CROWD FUNDS PRODUCTION

The 2000 Octopus Initiative specification describes an unusually recognisable mechanism.

Consumers place orders.

Their money remains inaccessible to the creator.

Orders accumulate towards a declared minimum target.

If the target isn’t reached by the Long Stop Date, the product is dropped.

If the target is reached, production can proceed.

The document specifically records that the creator could not access funds until the minimum target had been reached, and later describes Octopus itself acting as stakeholder of funds until minimum orders were achieved.

This wasn’t conventional investment deciding what the public might want.

The public itself demonstrated the demand.

THEN THE NETWORK COULD BE NOTIFIED

Once a viable product existed, Datalink’s connected architecture offered another possibility.

Instead of the creator individually finding every route to market, the network already knew who the relevant participants were.

Retailers.

Manufacturers.

Suppliers.

Distributors.

Investors.

Customers.

The opportunity could therefore move through the network.

The contemporary specification explicitly envisioned retailers receiving product-performance information before deciding which products to move into mainstream business.

AND EVERYBODY COULD PARTICIPATE

The Octopus vision wasn’t simply about making commerce more efficient.

It was designed to change who gets access to economic opportunity.

The 2000 specification states the principle plainly: people should have the right to participate in the economy regardless of whether they were unemployed, homeless or on a low income. It proposed donated promotional space, deferred development assistance and public investment opportunities.

If someone couldn’t create a product themselves, they could potentially:

Support one.
Order one.
Invest in one.
Promote one.
Supply one.
Manufacture one.
Sell one.

The Crowd-Economy was therefore never supposed to mean:

Everybody becomes an inventor.

It meant:

Everybody can have a route into the value created by everybody else.

DON’T TAKE MY WORD FOR IT — LOOK INSIDE THE MACHINE

The historical record now survives at three distinct evidential levels.

1 — SPECIFICATION

What was conceived

Contemporary Octopus documents describe the system, its economic objectives, minimum-order mechanism, stakeholder structure, public participation, investment system, retail network and connected support infrastructure.

2 — ENGINEERING

What was built

Surviving Microsoft Access databases contain relational structures for content, businesses, contacts, components, suppliers, communications, addresses, media, pricing, accounts and orders.

The surviving schema exposes the relationships beneath the system.

Separate surviving implementation material even contains actual conditional program/formula logic rather than retrospective descriptions.

3 — OPERATION

What users could actually see

Surviving interface screenshots show the system populated with real businesses, products, components, suppliers, prices and associated information.

These aren’t three copies of the same claim.

They are three different forms of corroborating evidence:

DOCUMENTED → ENGINEERED → DEMONSTRATED

WHY DOES THIS MATTER TODAY?

Because the underlying problem never disappeared.

Creators still struggle to reach markets.

Small businesses still struggle to reach customers.

Manufacturers still need orders.

Consumers still pay layers of unnecessary cost.

Investment still tends to flow towards those who already possess access to capital.

And enormous amounts of potentially useful knowledge remain trapped inside disconnected organisations and databases.

Technology has advanced dramatically.

The economic architecture hasn’t.

THE MISSING ENGINE OF THE CROWD-ECONOMY

The Crowd-Device provides the mechanism:

Token → Threshold → Outcome

Datalink provides something different:

The interconnected economic environment in which those outcomes can actually happen.

One establishes collective demand.

The other connects that demand to the people, resources, information and infrastructure capable of fulfilling it.

Together they form the foundations of what we have been calling the:

CROWD-ECONOMY

Not an economy controlled from above.

Not an economy in which algorithms decide who deserves opportunity.

Not an economy where access depends upon already possessing wealth.

But an economy in which:

People create the opportunities.

People choose which opportunities succeed.

People provide the resources.

People share in the resulting value.

IT WAS BUILT THEN.

IT CAN BE BUILT PROPERLY NOW.

The technology available today could take what required an enormous bespoke relational system at the turn of the millennium and transform it into a global, real-time economic network.

The historic Octopus Datalink therefore isn’t being presented as the finished solution for 2026.

Datalink