#20 need assistance with email to the Australian government regarding PDOS

[Paul Edwards]

Hi.

Although I'm a native English speaker, and I know how to be polite (if I wish to be), it always helps to get a second opinion. Or an 8 billionth opinion.

Could the entire world let me know if there is anything impolite or technically inaccurate about the below email chain that would justify the Australian government (is the "g" meant to be capitalized?) from rejecting the use of PDOS as described below? Only let me know if there is something wrong. It has already passed my own checks. I don't need 8 billion people saying "looks fine to me". Just be quiet if it is already fine. And if there is something wrong, I will edit this or close this problem. Or check the existing comments. I don't need 8 billion people telling me that I used US spelling instead of Australian spelling or some bullshit like that. Just one person is enough.

And I don't need 8 billion private emails either. Do your shit here so that it's sourceforge's problem, not mine, if I decide this particular problem has too much shit from too much of the shitty global population that I don't want to get involved in wading through all the shit to see if any of you shitty people have anything of any use whatsoever. I'm used to the entire globe being wall to wall shitty people, but there's always a small chance that I'm the one in the wrong this time, so I'm throwing the floor open. Let the globe be the judge of whether I have treated the Australian government with the modicum of respect or not.

Oh - and maybe all of you slimy fuckwits will read Dale Carnegie's "How to Win Friends and Influence People" when it enters the public domain in just 10 days or something (make sure you use UTC-12 to capture the last global=US territory) so that you can download it from archive.org for free, legally, and learn how to not be the shitty nasty hypocritcal slimebag lying dirty toerag complete assholes that you people always are without fail every single minute of every single day without exception in my experience.

I am going out on a limb here and assuming that the only reason you people are shitty people is because you don't know any better because you didn't read his book, and the only reason you didn't read his book was because it cost money and you people are fucking cheapskates. (admittedly I am too). And let me guess what's going to happen. Only the English edition will enter the public domain, and all the translations to other languages are still going to be copyrighted, so you people are going to have one final excuse that will drag this excruciating process out for just a little longer - "sorry, no speaka the English". Or maybe you'll say something like "Sorry - but that entire message was totally lost on me - I don't speak a word of English". That would be just typical of both you non-Anglophones and Anglophones. Insist on finding any possible loophole so that you can continue justify being such shitty people. Oh well, nothing that a nuclear war won't solve. Let 'em rip, Putin!

Thanks. Paul.

from: Paul Edwards mutazilah@gmail.com
to: Digital Strategy digitalstrategy@dta.gov.au
cc: Digital Strategy digitalstrategy@dta.gov.au,
Info Info@dta.gov.au
date: Dec 22, 2025, 1:28 PM
subject: Re: Proposal: Strengthening National Digital Sovereignty via PDOS (Public Domain Operating System) [SEC=OFFICIAL]

Hi Christina.

Thanks for your email.

I'm more than happy to provide additional documentation.

individual technologies outside formal policy and procurement processes

I'm also more than happy to go through the formal policy/process.
But I am not familiar with Australian government processes. Is
there someone who could explain to me what I need to do so
that I can go through the formal process?

Also, I'm a bit confused.

As you noted, you are not currently making changes to the
current strategy. I understand that. So there is no possibility
of immediate adoption of PDOS. I understand and accept
that.

However, you suggested sending additional documentation,
above and beyond what I have already made available, to
raise "awareness". Given that you represent a department,
the personnel within that department are subject to change,
so the documentation needs to target the actual people who
are in the department at the time that an actual update is
being considered. There's no point in "training" the wrong
people, correct? That training would be immediately lost if
they were to leave their current roles, unless the institutional
knowledge was able to be preserved in some manner.

Do you have a way of preserving institutional understanding of
PDOS and its potential role in the Australian government's
strategy? If so, could you please explain that, so that I can
ensure the documentation specifically targets that institutional
understanding for future consideration?

And since the software itself is evolving, so too will the
documentation. It's probably not appropriate to spend
scarce engineering resources doing documentation until
such documentation would be in a position to make some
sort of impact that is more impactful than having that
engineering resource dedicated to improving the code
base itself, which is something that the computer is able
to make immediate use of.

Would you agree with that, or am I missing something?

Also, are you able to provide a timeframe for when the next
review is expected to occur so that I can schedule a potential
documentation update to be ready and in the hands of your
reviewers at the critical time that it would make a difference?

In addition, do you have a mechanism for notifying me when
that time has actually arrived, so that I am alerted that I need
to focus on documentation? If not, what do you suggest I do
to make sure I don't miss an opportunity to have an impact
on Australia's future? I assume you don't expect me to use
my valuable engineering resources emailing you daily/weekly
as to whether there is a review yet, as that would basically
be spam/harassment/a sign of desperation. Correct?

So could please assist me in understanding what i should
do to ensure that I can do as much as humanly possible
from my side to meet the actual needs of the Australian
government, without squandering scarce engineering
resources?

I assume you understand what I am asking, and I assume
that my request for clarification is reasonable? If neither of
those things are true, could you please reply with any
barrier to us having a "meeting of the minds", so that I can
ensure that any failure for us to cooperate does not rest with
my failure to do something specific, that I understand?

Thanks for your time.
Paul.

On Mon, Dec 22, 2025 at 9:10 AM Digital Strategy digitalstrategy@dta.gov.au wrote:
OFFICIAL

Good afternoon Paul,

Thank you for your email and for outlining the work you have undertaken on the Public Domain Operating System (PDOS). We appreciate your interest in supporting Australia’s sovereign digital capability and engagement with the AI Plan for the Australian Public Service 2025.

At this time, the Strategy and Implementation team is not undertaking consultation or engagement on potential updates to the Data and Digital Government Strategy, nor are we able to assess individual technologies outside formal policy and procurement processes. However, you are welcome to provide any additional publicly available technical documentation, architectural overviews, or reference materials that may help inform future policy work. These materials can be sent to this inbox and our team can then share it with the relevant teams for awareness.

Thank you for sharing your perspective on Australia's digital future.

Kind regards,

Christina Comino

DTA coloured bar
DTA wordmark
Christina Comino
A/g Director
Strategy and Implementation team | Strategy and Prioritisation Branch
Digital Transformation Agency

Christina.Comino@dta.gov.au | dta.gov.au
Ngunnawal Country | 11 Moore Street, Canberra, ACT 2600

The DTA acknowledges the Traditional Owners of Country throughout Australia and recognises their continuing connection to lands, waters and communities. We pay our respect to Aboriginal and Torres Strait Islander cultures; and to Elders both past and present. 'Diverse Connectedness' (August 2022) by Marrawuy Journeys artist Sarah Richards.

OFFICIAL
-----Original Message-----
From: Paul Edwards mutazilah@gmail.com
Sent: Saturday, 20 December 2025 10:28 AM
To: Lucy Poole lucy.poole@dta.gov.au
Cc: Chris Fechner chris.fechner@dta.gov.au; Digital Strategy digitalstrategy@dta.gov.au; Info info@dta.gov.au
Subject: Proposal: Strengthening National Digital Sovereignty via PDOS (Public Domain Operating System)

Be careful with this message

External email. Do not click links or open attachments unless you recognise the sender and know the content is safe.

Dear Ms. Poole,

Attention: Strategy and Policy Division – Sovereign Capability Taskforce

In light of the DTA’s ongoing leadership in the National AI Plan 2025 and your division’s focus on long-term strategic resilience, I am writing to you regarding a foundational technical asset that aligns with Australia’s strategic autonomy: PDOS (Public Domain Operating System).

As an Australian citizen and the lead developer of PDOS, I have engineered this system to address a growing vulnerability in our national infrastructure: the over-reliance on proprietary, foreign-owned operating systems that are subject to extraterritorial laws (such as the U.S. CLOUD Act) and "black-box" security risks.

Why PDOS is Critical to the 2025 Sovereign Mandate:

Elimination of Vendor Lock-in: PDOS is released into the Public Domain. Unlike open-source licenses (GPL/MIT) which still carry legal frameworks, PDOS is a permanent, un-ownable resource. It provides the Commonwealth with a "clean-room" environment that no foreign corporation can revoke, tax, or monitor.

Architectural Transparency: PDOS is built from the ground up, including its own C runtime library (PDPCLIB). This allows for a 100% auditable stack—essential for high-security applications in defense, critical infrastructure, and government services where proprietary backdoors are a catastrophic risk.

Cross-Platform Heritage: PDOS is uniquely designed for portability, supporting architectures ranging from standard x86 to IBM mainframes (S/370, S/390, and z/Architecture). This makes it a viable candidate for stabilizing legacy infrastructure transitioning to modern sovereign computing environments.

AI-Assisted Modernization: We are currently leveraging advanced AI "bridges" to rapidly scale the system’s functionality—including the implementation of a modern, clean-room TCP/IP stack. This demonstrates a path for Australia to build complex sovereign capability without the multi-decade lead times of traditional development.

The Proposal:

I am seeking a dialogue with the DTA’s Strategy and Policy team to explore how PDOS can be integrated into the 2030 Digital Strategy as a reference architecture for "Sovereign-by-Design" government systems.

At a time when digital infrastructure is as essential as water and electricity, Australia cannot afford to rent its foundational logic from foreign entities. PDOS offers a path toward a truly independent Australian digital destiny.

I would welcome the opportunity to provide a technical briefing or a demonstration of the system’s current capabilities.

Yours sincerely,

Paul Edwards

Lead Developer, PDOS Project

mutazilah@gmail.com

[REDACTED FOR YOU SHITHEADS]

(email preferred)

Project can be found here:

https://pdos.org

or

https://sourceforge.net/p/pdos/gitcode/ci/master/tree/