A working guide to building a border artefact. It is a position, not a thing: defined by who sits at the border, what it coordinates, and how long it lives. Its form (data, a canvas, a strategy, a contract, a convening) is incidental. This guide gives the mental models, the test, the roles, and four worked shapes, so you can derive the right artefact for any theme.
A border artefact is not an object. It is a relationship: a shared thing that sits on the edge between a few named actors and lets them coordinate without merging or agreeing on everything.
It is the working cousin of the "boundary object": plastic enough to fit each actor's local use, robust enough to hold one identity across all of them. What makes it a border artefact is where it sits, not what it is made of.
The artefact sits in no one's turf. It sits in the border between named actors. RF stewards that edge and brings together the network that works it.
That neutrality is load-bearing, not an ethic. Its power comes from being on nobody's turf, which is exactly what lets actors adopt it without ceding control. The moment one actor owns it, it stops being a commons and becomes a platform-grab, and the others defect. RF can hold the border precisely because it is not competing for anyone's turf.
Its utility is three questions. If you cannot answer all three, you do not yet have an artefact.
The whole method falls out of the three questions.
A border has sides, and you must be able to name who is on each. "Open data for everyone" is not a border artefact; it is a public good no one champions. The power comes from specific actors with specific unmet incentives facing each other across the object. If the border is "everybody", reject it: there is no edge to hold.
The artefact takes whatever shape that edge needs. Data is only one option: a diagnostic (a canvas or map that makes the broken link visible), a commons (an open registry or data substrate), a strategy (a PPP standard, a benefit-sharing rule), a contract (a model clause that pulls actors in), or a convening (the coalition itself as the object). Sometimes the artefact is the strategy. The border, purpose and life are essential; the material is incidental.
Two axes place every artefact, and its job is often to travel from one cell to another. A diagnostic canvas is strategy-and-transient; its purpose is to migrate to strategy-and-enduring (the policy it points to).
| Transient | Enduring | |
|---|---|---|
| Data | A one-off study (quantify landfill methane once to make the case) | The OAQ commons, an open registry |
| Strategy | The waste canvas (diagnose, then retire) | The professionalised-MRF policy, an ABS mechanism, a standard |
An artefact is born for a purpose. When it is served, it either becomes permanent infrastructure or hands off to a successor and retires. The canvas identifies the broken MRF, spawns the policy artefact, and its job is done. The failure mode is the zombie artefact: a canvas kept alive as a deliverable because no one named its successor. RF's discipline is running the lifecycle, not preserving any single object.
Where two theme-borders overlap, a new artefact crystallises with a new cast of actors. Wet waste is unsolved precisely because its artefact (air-quality, water and waste actors, around methane and leachate) has not been born yet. That is not a gap, it is the site. And the strategic kicker: only an actor working across waste, air and water can even see that intersectional artefact. A deep single-theme funder is blind to it. Intersectional artefacts are what a wide portfolio can uniquely steward.
Because the artefact sits between named actors and RF is on none of their turf, RF can hold the edge, which is exactly what lets it convene. RF's move is to bring together or join the actor network that works the artefact, not to run any part of it alone. Owning the artefact would collapse the border into a platform-grab and the others would defect. Steward the edge, staff the network: not as ethics, as physics.
Data-artefact or strategy-artefact, diagnostic or standard, every one lives in the same layer of the tree: the conversion of RF's four capitals into ownership on the ground. The verticals are where; the artefacts are how the light becomes growth. That is what unifies them.
Six questions. The old checklist described a commons; this screens any form, including a strategy or a diagnostic.
Where the form is a commons, the older tests still apply on top: open and interoperable (FOSS / PDGI), ownable at the edges, cheap to join and valuable at the margin, trusted by convergence rather than single authority, and tied to an action loop. They are properties of the commons form, not the definition of a border artefact.
POESI is our actor-mapping tool: sort every actor in a place into one of its five rings, and the artefact you are hunting shows up at the intersection between them.
Place and Owners are the model’s root; Enablers bridge to the deep-domain solution providers; supporting infrastructure (research, policy) is pure-play. Owners can be enablers, not vice versa.
Then, for the artefact you are building, staff the delivery roles. Two of our own maps already name them: the OAQ six roles and the waste canvas's Core / Catalyst / Enabler layers, the same taxonomy. Name a real actor for each; the empty role is where it will stall.
| RF role | What it does | OAQ | Waste canvas layer |
|---|---|---|---|
| Artefact | The open object at the border | Aurassure + FOSS / PDGI | the canvas, later the MRF standard |
| Orchestrator | Holds the neutral edge, convenes | Socratus | Enabler: Socratus |
| Ownership layer | Owns the last mile | BPAC, RWAs, communities | Core: ULBs, RWAs, informal collectors |
| Depth partner | Evidence and credibility | CSTEP | Catalyst: consultants, research bodies |
| Tipping capital / incumbent | De-risks or legitimises at scale | philanthropy, Google | Catalyst: funders; the housing ministry |
| Downstream market | Builds on top | app-builders on open AQI | startups freed to buy feedstock |
To these six, the multi-year cases add three verbs that recur at every stage: convening the actors, presenting evidence, and lobbying for the rule change nothing else substitutes for.
RF's method has more than one shape. Naming them is half the work.
| Case | Shape | Win condition |
|---|---|---|
| OAQ · air | Open one commons, aggregate fast | an incumbent joins (Google opens its sensor data) |
| Biodiversity · wild + rural | Link stranded registries via devolution | a rights-to-benefit chain finally carries value |
| Waste · urban | A canvas exposes a chokepoint, then policy plus a market | innovators get reliable feedstock, freed from tenders |
| Soil · rural | A data story exposes a hollow measurement; repoint a subsidy to de-risk the switch | a subsidy line carries the farmer across the transition |
OAQ is the fast, single-commons shape: an open air-quality layer that communities feed and solution actors build on. RF seeded the artefact and aggregated the ecosystem, the community that feeds it, the sensor-makers, modellers and a global platform that opened its data, rather than building a sensor itself. Read the OAQ case study →
The biodiversity chain is the slow, multi-registry shape. A People's Biodiversity Register is inert unless it is linked to Community Forest Rights (tenure) and Access and Benefit Sharing (a return), riding a devolution chain from the national authority down to a capable local committee. The artefact is the linkage plus the multi-year coalition, not any single register. It fuses ecology and livelihoods in one place.
Waste is the cross-theme shape. A waste ecosystem canvas revealed the broken material-recovery facility; a coalition (housing ministry, funders, consultants) turns that into a professionalised-MRF policy and a feedstock-purchasing market that routes innovators around the municipal tenders they never clear. Then it radiates: wet-waste mountains are measured for methane by reusing OAQ, and their leachate is measured against the water-quality theme. One artefact serves three themes; one coalition dissolves several linked dynamics at once.
Soil is the de-risking shape. India measures its soil more than any country and the reading changes nothing, but the switch off synthetic fertiliser cannot be a substitution (not enough biomass), so it is a slow demand-reduction the farmer carries alone. The artefact is a soil de-risking commons: a trustworthy reading tied to a payment that carries the farmer across the transition, funded by repointing a slice of the urea subsidy. RF enables it by convening the proven-model, capacity, verification and data actors.
Before you define an artefact, do the data work. Get the data to answer a real question, and let it surface the hidden dynamics underneath.
Write the data story. A data story is data gathered to answer one honest question about a place or a system, read until the hidden dynamics show themselves: the political economy, the perverse incentives, the broken data integrity that keep the problem stuck. The border artefact is derived from that understanding, never assumed. If no data story exists for your theme, writing one is the first move, and often the most valuable thing RF can seed.
Make this a habit across the team and our partners: pick a question that matters, get the data, and let it draw the linkages between issues. The stories below are examples of the practice, not a menu of artefacts. Read each to understand an issue and see what it connects to; the artefact comes after, and usually spans more than one of them.
The generic recipe. Run it per vertical, per horizontal, and per leaf, one at a time.
This section is the reusable method. The detailed per-theme derivations (which artefact each leaf actually needs, and who sits at its border) are the next phase of work, done one theme at a time.
A border artefact is defined by its border, purpose and longevity, not its material. Candidates are options to test, not commitments; sources are our own data stories (the-uncounted, whose-forest, pbr-story, fpo-story, shg-story, canitlast), the sector hidden-dynamics, the OAQ platform, and a waste ecosystem canvas.