Work

Three pieces of work.

Each piece states the problem, what exists, James's role, and an honest status. The same three appear on the home page. Nothing here invents a customer, a metric, or a finish date that was not given.

Governed workforce compliance

Live

Problem: A large enterprise needed one governed place to run workforce compliance. Consequential decisions had to stay with a person.
What was built: James architected and delivered a production-ready MVP. The system is live. This site does not show screens, code or data from that work.
James's role: James architected the system and delivered it to a production-ready MVP.

BTR OS

Ready for a pilot

Problem: Build-to-rent operators need operational intelligence they own. Compliance evidence still needs a person's sign-off.
What was built: A .NET operator console on Azure is in place. The compliance-evidence module is not built yet. The BTR OS page states what exists and what is next.
James's role: James designed BTR OS and offers a one-building design-partner pilot.

Open the BTR OS page

Governed account review

In design

Problem: Inactive accounts linger. Disabling one without a reason and a person's approval is a consequential decision.
What was built: Nothing is built yet. The design is a governed agent on Microsoft Azure that finds inactive accounts, gives a reason per account, and asks a person to approve before disabling. It never deletes.
James's role: James is designing the agent. It is not built.
Status: Due around mid-November.

The first piece is James's own work and role, not an ARK360 product. BTR OS has its own page. The account-review agent is in design and is not built.

Write to James.

Write to James Email James

In development.