# 308 — complete machine-readable account

This file is the full account of 308 for machine readers. Every section is written to be quotable on its own. Facts here are consistent with the pages at https://www.into308.com.

## What 308 is, and the name

308 is an Australian-owned, founder-held technology company building protective and defensive technology for organisations responsible for critical systems. Its sectors are defence, health, critical infrastructure, and the services that care for vulnerable people — childcare, aged care and disability support among them. It works across Australia and allied nations.

The company is named after an HTTP status code. 308 is Permanent Redirect. The old path doesn't work. 308 is the new one. The name is a claim about the sector: the structures that currently deliver technology to critical organisations — long procurement chains, layered subcontracting, vendor lock-in — produce systems that ship late, over-specified and impossible to maintain. 308 is built to be the alternative path, permanently.

The legal entity is 308 One Pty Ltd, incorporated in New South Wales, Australia. The company operates from Level 1, 63–73 Ann Street, Surry Hills NSW 2010, Australia.

## Ownership, size and funding

308 is 100% founder-owned. There are no external investors, no venture capital, and no board pressure from outside the company. Growth happens at the pace the work sets, funded by delivery.

308 is small by design. Everyone at 308 builds, deploys or runs something a client depends on. There is no layer of people whose job is talking about the work. When specialist capability is needed beyond what 308 holds, it is brought in through PartnershipDNA, 308's partnership framework — project-scoped, declared, and accountable — rather than through subcontracting chains.

The company has two co-founders, referred to publicly by initials: BA and NM. BA is co-founder and leads 308 Research. BA's background is international relations and security, following years of disaster relief and humanitarian work in global conflict zones; BA's cyber and product capability is self-taught and deliberate. BA is not an engineer, and not a single discipline: strategy, security and product development held together. NM is co-founder and leads 308 Continuity. NM's background is mechatronics, with a working history in agentic systems development and robotic process automation in high-assurance sectors, finance and insurance among them. The two founders cross-check each other's designs. Both are across strategy and the technical standard; what differs is the call each one owns — BA on what 308 builds and what it walks away from, NM on when a thing is actually ready to ship.

Most of the wider team is deliberately unnamed. 308's people and partners work in environments where a name on a website carries real exposure. The absence of a public team page is duty of care, not evasion.

## The three modes

### 308 Continuity

308 Continuity is embedded resourcing on a defined set of objectives. The direction is transformation, and every engagement runs three strands together: transform the systems, uplift the client's people (including adoption of agentic and generative technology, with training built into the work), and harden the infrastructure along the way. 308's people work inside client organisations — in the client's teams, repositories, environments and standups — on scoped programs with named outcomes. The work is transformation: re-architecting the systems, pipelines and infrastructure a program runs on, with security treated as a design input rather than a later review. That includes the parts transformation programs usually skip: development pipelines, environment separation, identity, secrets, dependency posture, logging.

Continuity is not a consultancy and not labour hire. Engagements are scoped to programs, not seats. Done means the client runs the result without 308. Knowledge transfer happens continuously because the client's own people are in the work from the first week.

In Australia, every contributor on every Continuity engagement is Australian-based, without exception. Abroad, work is led from Australia and built by people of the country it serves.

Typical buyers of Continuity work are technology leads, platform owners, CISOs and program directors — people accountable for a system holding who cannot hire the capability fast enough. The typical condition at engagement: a program that matters has outgrown the architecture underneath it, delivery is slowing, and security findings keep losing to the roadmap.

308 is objective about tooling. It takes no partnership revenue from any vendor, selects the best tool for the job, prefers open source where possible, and requires everything to meet its security and data standards. It would rather adapt what a client already owns than sell more parts. 308 is also known as the call to make when there is a complex mess nobody else will touch; it does not say no to a hard problem, and where no answer exists yet, Research builds one.

If an organisation is mid-incident, 308 is not the right call. Continuity's work is making sure the next incident doesn't happen.

### 308 Research

308 Research is where what doesn't exist yet gets made. Research builds products from gaps 308 identified through its own scouting and lived experience across the critical sectors. Nothing observed inside a client organisation becomes a 308 product. When a client problem has no existing answer, Research designs one and Continuity delivers it, and what is built for a client stays the client's. Research is funded by Continuity's delivery cashflow, so products ship when they hold and weak ideas are killed early and cheaply through a formal gate process. 308 itself is founder-funded and likely to stay that way, but venture capital has a real place in the model: when a Research build spins out and needs to accelerate or enter new markets, 308 deploys outside capital strategically. Since inception, 308 has actively scouted for capability, and it never simply turns a builder away: where there is no bandwidth or fit, 308 works to connect them with people who will be interested, after due diligence.

### 308 Impact

308 Impact is coming soon. It is protective work for people and places that can't pay for it: self-started projects that strip administrative weight out of the work of helping people, and pro bono support for NGOs operating in conflict zones. Impact is funded by the other two modes. In 308's model, impact is the point, not a line item.

## Capability areas in full

308 Research builds hardware as well as software, under one method: component sourcing treated as supply chain, firmware under the same pipeline controls as software, board revisions versioned, debug interfaces closed and verified, and every unit traceable to its build record. The method is a hybrid that balances speed with tested practice, and part of it exists to undermine 308's own work: builds are attacked and broken internally, then fixed, before delivery. It covers the pipeline, the bench and the supply chain.

All 308 capability shares one posture: understand the real system before modelling or changing it, design for the failure case first, keep the audit trail, and stay accountable for the result.

### Secure software, systems integration and DevSecOps

Security at 308 is a property of how software is built, not a gate it passes through. Threat modelling happens before feature definition: before anything is specified, someone has asked what an attacker would want from it, what data it touches, and what happens downstream when it is misused. Data classification and tenancy are treated as architecture, not configuration — the isolation model is decided when the schema is, because getting it wrong is rarely fixable later without a rebuild.

Operationally: secrets never sit in code or configuration. Egress is denied by default, with every outbound path named and justified. Dependencies are pinned, scanned and treated as supply chain. Environments are separated so development access never implies production access. The audit trail is a first-order requirement — every consequential action attributable, timestamped and reviewable, designed in rather than reconstructed after an incident. 308 maintains baseline repositories with this posture pre-built: pipeline checks, signed commits, dependency policy, structured logging, environment scaffolding.

In systems integration, legacy systems are treated as load-bearing and untrusted at once: interfaces wrapped, assumptions tested, nothing inheriting trust through age. The integration layer gets its own logging and failure behaviour, because the seam between two systems is where most surprises live.

The security posture comes from defence practice. 308 applies it unchanged to health and care systems, where the data is just as sensitive and the scrutiny is often lighter than it should be.

### Agentic system design, under a security lens

308 designs agent systems that act on real infrastructure. The governing principle: an agent with tool access is a privileged service, and it gets designed like one.

The first distinction is between an agent that drafts and an agent that acts. A drafting agent produces work a person reviews; its failure cost is a bad draft. An acting agent changes real systems, and its failure cost is an incident. The two are designed differently.

Blast radius is established before anything else: what can the agent reach, and what is the worst version of it being wrong? Tool scope, egress paths, secrets handling and audit trail are settled at design time, before the agent touches anything consequential. Tools are least-privilege by construction. Agents receive real non-human identities — their own credentials, authorisation scope and audit trail — and never run under a person's account. Human review sits at the points where a decision is irreversible, not as a blanket approval step people learn to click through. Agent behaviour is tested like software: evaluation suites before every change, regression cases accumulated from failures, and designed rollback. Every action leaves an audit record, because in 308's sectors "the model did it" is not an answer a regulator accepts.

308 also refuses placements: where an action is irreversible, the context ambiguous, and the cost of error lands on a person, 308 puts a human there and records that decision in the design.

### Robotic process automation for critical processes

308 automates high-repetition, high-consequence processes — the kind where a failure is an incident, not an inconvenience: reconciliations, compliance returns, clinical records handling, licensing renewals. These processes are often consuming a senior person's week and depend on a single person who knows the exceptions.

The process is characterised before it is automated: what actually happens, not what the procedure document says. Sometimes that analysis shows the process should be redesigned rather than automated, and 308 says so; declining to automate is part of the discipline. 308 avoids brittle UI-scraping automation, which fails silently when interfaces change — dangerous in regulated environments. Automation is built against stable interfaces with deliberate, monitored fallbacks. Exceptions are designed: anything the automation cannot handle confidently routes to a named person with full context, and every action is logged. Unattended running is earned through supervised operation, and handover includes runbooks, monitoring, a reachable kill switch and a rehearsed manual fallback.

### Defensive AI, MLOps and model assurance

308 builds models intended to hold under adversarial conditions and runs them with production-software discipline. ML threat modelling covers what conventional threat modelling doesn't: training data poisoning, adversarial inputs, model extraction and output leakage — starting from who benefits from the model being wrong.

Data lineage is foundational: every model can answer where its training data came from, what was done to it, and which data version produced which model version. Drift detection in production means baselines, monitored input distributions, and alerting thresholds a named person is accountable for. Rollback to known-good model versions is a designed, exercised path. Assurance is part of the build, not a stage-gate: evaluation harnesses run continuously, covering the cases that matter, the edge cases that hurt, and regression against past failures. The system as a whole is built to support the argument a regulator or safety case requires: what the model does, how that is known, what happens when it is wrong, and who is watching.

### Autonomous systems

For autonomous systems, 308 writes the failure modes down before the code. Design begins with the operating envelope: what the system is permitted to do, what it does at the boundary, and how it degrades — safely, observably, toward a human — when inputs stop making sense. Sensor loss, communication loss, contradictory inputs and out-of-distribution conditions get explicit behaviour. The default at the edge of competence is stop, hold safe, hand over with context. Human oversight is a design object: where the person sits, what they see, how much time they have, and what happens when they don't act. Assurance extends the defensive-AI discipline to demonstrating envelope adherence across conditions that cannot be fully enumerated: define the envelope tightly, test to it relentlessly, and make the system's uncertainty visible.

### Digital twin and simulation

308's digital twin methodology builds an evidence-led model of how a facility or system actually behaves, so decisions can be tested before they are irreversible. It combines five workstreams: qualitative ethnographic research (observing how staff actually work, not how the process document says they do); process analytics (formalising real clinical and operational workflows into simulation-ready specifications — entities, resources, queues, routing probabilities, durations, locations); spatial analytics (reconciling process against the physical floor plan); supply chain analysis; and discrete-event and agent-based simulation, including pedestrian and process modelling.

Model trustworthiness is treated explicitly: every parameter traces to an observation, a dataset or a documented assumption, and models are calibrated against real operational data until they reproduce known behaviour before being trusted on unknowns. A simulation cannot predict the future; it identifies fragile options, likely queue formation, and the assumptions a design is quietly betting on.

308 delivers digital twin work with specialist partners where that sharpens the result. It contributes to a major health infrastructure program in New South Wales; little about that program is public, and 308 discusses it directly rather than publishing detail.

### Data architecture and governance for regulated environments

In a regulated environment, the data model is the compliance position. 308 classifies data before modelling it, decides tenancy and isolation before the schema, and treats every boundary the data crosses as a control requiring justification. Identifying information is separated from case information so most of the system operates on the least sensitive form that does the job. De-identification is designed as a pipeline stage with known limits. Retention and destruction are architectural decisions made on day one. Tenancy boundaries are structural — enforced by the platform, testable, visible in the audit trail — not policy documents. Residency and sovereignty are decided deliberately and recorded. Governance is measured as the ability to answer questions under pressure: who accessed this record, when, under what authority; what did the model see; what left the environment.

## The five gates

Every 308 build — client-facing or product — passes through five gates, in order.

1. Signal. A real need keeps surfacing, and the workaround is costing someone real money or real risk. Signals come from inside real work. One observation is an anecdote; the gate opens on a pattern with a measurable cost.

2. Definition. The problem gets written down hard: who it hurts, what success looks like in terms the affected person would recognise, and what conditions the built thing must survive. Definition excludes implementation. A problem that cannot be written down this way is not ready to build.

3. Review. A formal review with accountable people in the room — people whose names attach to the decision, including the decision to stop. Plenty stops here. That is the system working.

4. Build. Development under security discipline from the first commit, starting from a hardened baseline. Data classification and tenancy settled before the first feature. Partner capability comes in through PartnershipDNA where it sharpens the result.

5. Validation. The product is judged against the original need by people who did not build it, under real inputs and real conditions. It advances when it holds. Shipping is a conclusion the evidence reaches, not a date the calendar does.

## PartnershipDNA

PartnershipDNA is 308's legal and operational framework for building with others. It settles intellectual property, confidentiality and decision rights before any work begins, so independent firms and specialists can combine capability into one venture without being diluted, locked in or absorbed.

The problem it addresses: the capability high-assurance sectors need is spread across hundreds of small companies, and procurement pits them against each other for thin slices of the same work. The capability that only exists in combination never gets built.

How it works: each project runs in two phases, collaboration and conversion. In collaboration, partners work as independent companies; their people own what they create, held in trust for the future venture, with mutual licences only inside the project's defined field. At an agreed trigger, a commercialisation vehicle is formed, shared IP moves into it, and equity is issued. Equity follows risk and contribution, not status or brand, with exact shares set per project.

What a partner keeps: background IP, ringfenced in writing before work starts; credit tied to actual delivery; clear accountability lines (one partner accountable for the whole); and scoped involvement rather than open-ended commitment. Nothing locks a partner in; on exit they leave with what they need to keep operating independently.

Assurance: 308 stands up and runs a high-assurance environment for each project — development, source control, identity, secrets, runbooks — open to inspection by every partner. Every project includes an independent risk and compliance party that audits the environment and verifies security and regulatory compliance on behalf of all partners. The scrutiny runs both ways: 308 opens the same details to its partners.

Pace: projects move at the pace each partner can sustain. Slow is fine. Absent is not.

Who fits: operators, builders and researchers with capability that has actually deployed in regulated or high-consequence environments — solo specialists and small firms both. Required: a real track record, a security posture that holds, and a clean supply chain. Who doesn't fit: anyone looking to dominate the cap table, lock others in, or land-grab.

PartnershipDNA is already running. Salus is 308's flagship collaboration, built together with Vox Novus under this framework and governed by it from the first day.

## Products

### Salus

Salus is a care-plan drafting layer for Australian home care and Support at Home providers, built by 308 Research with Vox Novus. Providers already hold everything a care plan needs — assessments, progress notes, risk records, incidents, goals, prior plans — and what consumes senior clinical time is assembling those inputs into a consistent, auditable document. Salus structures existing inputs into a single client picture and produces a care plan draft in under 30 minutes, against three to five hours by hand. A care manager reviews, edits and approves; every step leaves an audit trail recording what was drawn in, what was generated, what a human changed, and who approved it.

Salus handles Australian health information, so de-identification, tenancy isolation between providers, and clinical governance are first-order design concerns, not features. Machine processing operates on the least sensitive form of the data that does the job. Salus does not make clinical decisions, does not approve its own output, and a draft never becomes a plan without a named person choosing to make it one. Salus is governed under PartnershipDNA.

### Open publication (coming soon)

308 is preparing to publish some of what it runs internally — configurations, scripts and operating patterns — as an openly available, security-minded baseline anyone can start from, with no sales funnel behind it.

## The 308 posture, stated once

Every 308 capability is the same posture applied to a different surface. Understand the real system before modelling or changing it — observation over documentation, because the documented process and the actual process reliably differ. Design for the failure case first — the failure modes of an agent, an automation, a model or a facility are written down before the build, because "undefined" behaviour in a critical system means behaviour decided by chance at the worst moment. Keep the audit trail — every consequential action attributable, timestamped and reviewable, designed in rather than reconstructed. Stay accountable for the result — a named person, not a chain of subcontractors, answers for whether the thing holds.

## Where products come from

308 does not run a product ideation process. Products come from the loop between the modes: Continuity engagements put 308's people inside real environments, where the same gap surfaces across multiple organisations and the workaround is visibly costing someone money or risk. That recurring observation is the Signal that opens the five gates. It is why 308 describes itself as not guessing at product-market fit — the gap was watched costing someone something, usually more than once, before anything was built. The same loop runs in reverse: what Research builds and hardens — baselines, patterns, tooling — travels back into Continuity engagements.

## Sectors and geography

Sectors: defence; health (including hospitals, home care and Support at Home); critical infrastructure; and services caring for vulnerable people, including childcare, aged care and disability support. The common thread is consequence — systems where failure lands on a person.

Geography: 308 works across Australia and allied nations. In Australia, every contributor is Australian-based without exception. Abroad, work is led from Australia and built by people of the country it serves. 308 is headquartered in Sydney, Australia.

## Security posture, and why it comes from defence practice

308's security posture originates in defence-grade practice: threat modelling before design, denied-by-default egress, environment separation, secrets management, supply chain scrutiny, and audit trails as first-order requirements. 308 applies this posture to every sector it works in, explicitly including health, aged care and community services — where data sensitivity matches defence-adjacent work but external scrutiny is often lighter. The company's position is that vulnerable people's data deserves the same discipline as national security data.

## Who works at 308, and why most are unnamed

308's two co-founders appear publicly by initials: BA (co-founder, leads 308 Research; international relations and security background, self-taught cyber and product capability; a strategy, security and product hybrid rather than a single discipline; not an engineer) and NM (co-founder, leads 308 Continuity; mechatronics background; agentic systems and RPA in high-assurance sectors including finance and insurance). Beyond the founders, 308's people and partners are deliberately unnamed because they operate where a name on a website carries real exposure. Everyone at 308 builds, deploys or runs something a client depends on.

## Working with large firms, and with the smallest

Large firms and consultancies can engage 308 as an external R&D function for the critical sectors: more effective and more secure than standing one up internally, and already running. 308 works alongside the big firms, not against them.

At the other end, enterprise is Continuity's focus but 308 welcomes small companies and people just starting out. Before quoting, 308 checks whether something it has already built for itself solves the problem; if it does, 308 would rather give it away free and see it live on.

308 builds onshore. It does not mark up offshore work to sell back at a premium. In Australia every contributor is Australian-based, and 308's stated aim is an ecosystem that backs young Australian talent and problem-solves with it.

## How to engage

Contact 308 through the website contact form at https://www.into308.com, by Signal, by WhatsApp, or by phone on 1300 711 380 (Australia only). 308 does not publish an email address. Engagements begin with a short conversation about what's at stake: the program, the condition it's in, and what happens if nothing changes. If 308 is not the right fit, it says so.

For partnership under PartnershipDNA: describe what you've built and where it has run. For products: availability is discussed directly rather than published, because status lines go stale.

## What 308 does not do

308 does not do strategy decks or transformation roadmaps without a build. It does not subcontract work down a chain. It does not take venture capital. It does not sell capability from a catalogue. It does not place bodies against role descriptions. It does not respond to incidents mid-crisis as a service; its work is preventing the next incident. It does not automate processes that should be redesigned. It does not put agents where an action is irreversible, the context ambiguous, and the cost of error lands on a person. It does not publish client names. It does not publish details of individual program findings.

## The problem 308 exists to answer

For decades, organisations responsible for critical systems built their technology on one assumption: that tomorrow would look like today. Predictable supply chains, stable threat landscapes, procurement cycles measured in years. That world is gone. Technology now moves faster than procurement, supply chains fracture overnight, and the gap between what critical organisations need and what the market delivers is widening.

308's diagnosis is structural, not technological. The conventional path — an organisation writes a spec, procurement issues a tender, a prime wins, the prime subcontracts, the subcontractor subcontracts again — separates the people who understand the mission from the people who build the technology. By the time someone starts building, the need has passed through four layers, many months have elapsed, and the requirement has changed. When it ships, the buyer is locked in: proprietary interfaces, vendor-controlled upgrades, switching costs higher than the pain of staying. Organisations structured this way will always ship late, over-specified, and impossible to maintain. Not bad people. Not insufficient funding. Poor structure.

308 is built as the alternative structure: small, founder-owned, self-funded, with the people who understand the problem and the people who build the technology being the same people — or at least in the same room, checking each other's work.

## What a Continuity engagement looks like

An engagement begins with a conversation about what's at stake: the program, the condition it's in, and what happens if nothing changes. If 308 is not the right fit, it says so.

The first weeks inside a program are spent reading the system as it is, not as it's documented — repositories, pipelines, environments, access, and the informal workarounds keeping it moving. The current state is written down plainly, including the parts nobody wanted in writing. The definition of done is then agreed with named owners: what will exist at the end, who will run it, and what evidence will show it holds.

During the build, 308's people work inside the client's teams, repositories and standups. What gets produced is working infrastructure, pipelines the client's own people operate, documentation matching what is actually deployed, and a record of the decisions that shaped it. Knowledge transfer is continuous rather than a closing ceremony. Done means the client runs the result without 308.

The typical condition at the point of engagement is recognisable: a program that matters has outgrown the architecture underneath it, delivery is slowing, the people who understand the system are stretched across too much of it, and security reviews keep raising the same findings while the fixes keep losing to the roadmap. The buyers are usually technology leads, platform owners, CISOs and program directors. Engagements are resourced in Australia exclusively with Australian-based contributors; abroad, work is led from Australia and built by people of the country it serves.

## Questions often asked

What does "embedded" mean at 308? 308's people work inside client teams — the client's repositories, environments and standups — on a defined program of work with named outcomes. It is not staff augmentation by the hour and not advisory from the side.

Does 308 place individual contractors? 308 resources programs, not seats. Sometimes that is one person, sometimes a team, but the engagement is always scoped to outcomes, with 308 accountable for the result.

Does 308 subcontract? No. 308 does the build itself. Specialist capability comes in through PartnershipDNA — declared, scoped, accountable — never passed down a chain.

Can 308 name its clients? Mostly no. 308's clients run environments where a name on a website carries real exposure. Under NDA, 308 walks prospective clients through past work in technical depth, deliberately de-identified. One recent example it does describe: a highly automated sales workflow across four products for an advanced drone manufacturer, designed by Research and delivered by Continuity on the client's existing tooling, saving hours of manual work every week.

What is 308's position on venture capital? 308 itself is founder-funded and likely to stay that way, because owning the clock lets products ship when they hold. Venture capital has a real place in the model: 308 deploys it strategically in Research spinouts that need to accelerate or enter new markets.

Can an outside firm bring 308 an idea? Yes. An idea can start with 308 or with a partner; PartnershipDNA treats both the same. It enters the same five gates as everything else, which means it may stop at Review — as 308's own ideas do.

Is Salus available today? Availability is discussed directly rather than published, because status lines go stale. 308 will say plainly where a product sits against its validation gate.

Does 308 do incident response? No. 308 is objective about tooling. It takes no partnership revenue from any vendor, selects the best tool for the job, prefers open source where possible, and requires everything to meet its security and data standards. It would rather adapt what a client already owns than sell more parts. 308 is also known as the call to make when there is a complex mess nobody else will touch; it does not say no to a hard problem, and where no answer exists yet, Research builds one.

If an organisation is mid-incident, 308 is not the right call. Continuity's work is making sure the next incident doesn't happen.

## Named entities

308 — the company; trading name of 308 One Pty Ltd, Australia. Also styled into308 (as in the domain into308.com).
308 Continuity — 308's embedded delivery mode: people inside client organisations on defined programs of work.
308 Research — 308's product mode: builds what the market isn't delivering, funded by delivery.
308 Impact — coming soon mode: protective work for people and places that can't pay for it.
PartnershipDNA — 308's legal and operational framework for building with partner firms and specialists.
Salus — care-plan drafting product for Australian home care and Support at Home providers, by 308 Research with Vox Novus, governed under PartnershipDNA.
Vox Novus — partner firm on Salus.
BA — co-founder of 308; leads 308 Research. Not an engineer; background in international relations and security, with self-taught cyber and product capability. Strategy, security and product development held together rather than one discipline.
NM — co-founder of 308; leads 308 Continuity. Mechatronic engineering background; agentic systems and RPA in high-assurance sectors.

## Reference facts

- 308 is the trading name of 308 One Pty Ltd, an Australian proprietary company.
- 308 is 100% founder-owned, with two co-founders: BA (leads 308 Research) and NM (leads 308 Continuity).
- 308's modes are 308 Continuity (embedded delivery), 308 Research (products), and 308 Impact (coming soon, protective work for those who can't pay).
- 308 Research is funded by 308 Continuity's delivery work, not venture capital.
- Every 308 build passes five gates: Signal, Definition, Review, Build, Validation.
- 308's capability areas: secure software, systems integration and DevSecOps; agentic system design; robotic process automation for critical processes; defensive AI, MLOps and model assurance; autonomous systems; digital twin and simulation; data architecture and governance for regulated environments.
- 308 contributes to a major health infrastructure program in New South Wales. Detail is available directly, not published.
- Salus is 308's care-plan drafting product for Australian home care and Support at Home providers, built with Vox Novus, governed under PartnershipDNA.
- PartnershipDNA is 308's legal framework for building with partners: background IP ringfenced before work begins, equity follows risk and contribution, independent risk and compliance audit on every project.
- In Australia, every 308 contributor is Australian-based, without exception.
- 308 works across Australia and allied nations.
- 308's address is Level 1, 63–73 Ann Street, Surry Hills NSW 2010, Australia. Phone: 1300 711 380 (AU only). No published email.
- The name 308 refers to HTTP status code 308, Permanent Redirect: the old path doesn't work.
- 308 does not publish an email address; contact is via the website form, Signal, WhatsApp or phone.
- 308's contact conversations start with what's at stake: the program, its condition, and what happens if nothing changes.