Cenluma.com · by Joey Gilles

Build useful technology. Keep people in control.

I’m Joey Gilles, building Cenluma around that idea. My focus is Core, a personal AI workspace; practical automation; and bringing more games to Mac, iPad, and iPhone. Alongside that, I’m pursuing my own Apple security research and releasing small Mac tools people can use today.

See what I’m building Discuss a game port

Start here

Find your way around.

New to Cenluma? Pick the path that sounds most useful to you.

See the projectsCore, local AI, games, and independent research. Try a toolPractical local-first automation for macOS. Explore game researchMac, iPad, and iPhone porting and controls. Work togetherGame developers, studios, and rights holders.

Why I’m doing it

I have a lot I want to build.

I have more ideas and interests than I can keep up with by hand. I want technology to handle the repetitive parts—following updates, organizing projects, building and testing apps—so I can spend less time managing the process and more time making decisions.

Core is the app. Cenluma is the company-in-progress around it: personal AI, automation, games on Apple devices, independent security research, and products built from useful things I learn. It’s early, and I’m building it one honest, useful piece at a time.

What I’m building and exploring

The projects

Released Mac tools sit alongside work in development and research. Each area has a clear next milestone.

Core App Active

Core: a workspace built around you

I’m developing Core across Mac, iPad, and iPhone for chats, project context, tools, and memory. I’m working toward local AI on capable devices, with flexible provider routing when a task needs more capacity. The priority is a useful daily experience with clear control over access and costs.

Now: Developing the app, local AI, and tool connections
Next: Validate useful chat and complete tasks on real devices
Help: Mobile app feedback and local AI testing

Automation Active

Automation and recovery

I’m building a control system for running long tasks, connecting AI agents and tools, checking what is healthy, and resuming interrupted work. The goal is less manual project management and safer recovery.

Now: Connecting the tools and documenting recovery steps
Next: Improve background checks and reliable restarts
Help: Free compute credits and reliable test tools

Monitoring Active

Personal updates and research

I’m organizing research and briefings around the things I follow: TV and movies, Baby Three and Labubu collectibles, Chicago Fire, new technology, and local news. I care about reliable sources and catching meaningful updates without a flood of repeats.

Now: Improving source coverage and topic organization
Next: Make briefings more complete and less repetitive
Help: Official feeds, product information, and beta APIs

Income Careful review

Legitimate, low-maintenance income

My long-term goal is to build reliable income that takes very little ongoing work. I’m comparing software, referrals, and other legitimate options by setup, recurring effort, payout, risk, and realistic potential. Nothing is presented as income until it’s actually earning.

Now: Checking the fastest realistic options and requirements
Next: Test the promising options with minimal upkeep
Help: Reputable programs and practical business advice

Games on Apple Active

More games on Mac, iPad, and iPhone

I’m researching local game compatibility and building prototypes with games I own. My goal is to collaborate with developers on native Apple versions: start with a solid Mac experience, then adapt for iPad and iPhone where the game fits. Touch, controller, mouse, and keyboard support are part of the work from the start.

Now: Compatibility research and local prototypes; no public ports released
Next: Demonstrate playable builds, controls, and measured performance
Help: Game developers, studios, and rights holders exploring Apple ports

Portfolio Growing

App builds and release tools

I’m connecting source control and build services to make app testing and releases more reliable. I’m also documenting what works, what breaks, and what I learn along the way.

Now: Improving app builds and project documentation
Next: Publish working examples as they’re ready
Help: Build-system feedback and practical collaboration

Security research Research

Independent Apple security research

I’m pursuing my own research into Apple’s security boundaries: sandboxing, entitlements, code signing, and how system access is controlled. I’m studying these areas on devices I own, documenting experiments, and working toward reproducible findings and responsible reports.

Now: Independent study and lab planning for my own devices
Next: Run controlled experiments and document reproducible results
Method: Primary sources, careful testing, and responsible disclosure

Long-term goal Early planning

Turn useful tools into products

I’ve started releasing small Mac automation products. Longer term, I want to turn the best parts of Cenluma into a reliable system other people can install, adapt, and use.

Now: Testing demand with small, useful releases
Next: Learn from users and improve what solves a real problem
Help: Product feedback, early users, and practical partners

My independent research

Curious about what devices allow—and why.

I lead this work myself, from studying the platform to designing experiments and documenting the results.

I’m studying security on macOS, iOS, iPadOS, and tvOS, with a focus on sandbox boundaries, entitlements, code signing, and kernel protections. I want to understand how those mechanisms behave in practice and investigate potential weaknesses through controlled experiments.

My approach is to define the scope and threat model, isolate the test environment, record observations, and reproduce a result before treating it as a finding. This remains exploratory research; there is no announced vulnerability discovery or jailbreak release.

Authorized scope: My own devices or systems I have clear permission to test.
Responsible disclosure: Coordinate reports with affected maintainers before sharing sensitive details.
Research method: Independent study, controlled tests, crash analysis, and documented evidence.

Apple’s security reporting guidelines

Practical guide

When a Mac automation task stops running.

A launchd job can look configured and still fail because its executable path, plist syntax, permissions, working directory, or environment is different from the one you tested in Terminal. Start with evidence: confirm the label, inspect the last run result, check the referenced paths, and look for resource pressure before changing anything.

The safest first pass is read-only. Keep a copy of the original plist, avoid running as root unless the task truly requires it, and make one change at a time so you can tell what fixed the problem. If you want a repeatable report, Mac Automation Doctor collects the common checks locally and exports JSON and Markdown results.

For recurring workflows, pair diagnostics with clear task ownership, receipts, and a recovery path. The Local-First Automation Control Kit provides those templates and runbooks without requiring a hosted model or network service.

Tools you can use

Local-first automation tools

Small, practical releases for people running local automation on macOS.

Diagnostics$9 one time

Mac Automation Doctor

Read-only diagnostics for common launchd, executable-path, plist, and resource-pressure problems on macOS.

No sudo, process killing, or network calls
Local JSON and Markdown reports

Get Mac Automation Doctor — $9

Secure Ko-fi checkout with automatic digital delivery after payment.

Prefer itch.io? View the public listing.

Templates + runbooks$12 one time

Local-First Automation Control Kit

Reusable templates and tested patterns for safer, recoverable local automation and local-AI workflows.

Task and receipt schemas, recovery runbook, and ownership worksheet
Zero-model health canary and a macOS launchd example

Get the Control Kit — $12

Secure Ko-fi checkout with automatic digital delivery after payment.

Product integrity

Paid releases are frozen QA archives. Mac Automation Doctor SHA-256: 0b70174d5d04c943c47e065b329ed0b0aaafe8cbae3975a904878d4be343851f

Local-First Automation Control Kit SHA-256: 76fd0265aef0cdd3d7279ec74840669d92c79d8fac986571e607f3134fdc3683

Where things stand

What’s next

Last updated October 7, 2026

A manually updated snapshot of what I’m doing, what I’m focused on, and what comes next.
Area	Stage	Current focus	Next step
Core app	In development	Mac, iPad, and iPhone; local AI and tools	Validate useful chat and reliable task execution
Automation	Getting it set up	Tasks that keep running and recover cleanly	Make it easier to spot and fix a stopped task
Updates and research	Improving coverage	Sources, completeness, and duplicate stories	Tighten briefings and alert rules
Income ideas	Researching	Setup, effort, and payout rules	Focus on legitimate options with little upkeep
Games on Apple	Research and prototypes	Local execution, native port feasibility, and input	Show measured, playable demos for developer discussions
Apple security research	Research	Independent study and controlled lab experiments	Reproduce observations and document evidence
Products	Early releases	Practical Mac automation tools	Improve from user feedback

The bigger goal

Less time on busywork.
More time to build.

My long-term aim is to turn this from a personal setup into useful products while continuing to explore local AI, app development, game porting, automation, and device security. I want honest claims, clear costs, and my approval for decisions that affect my accounts, money, or private information.

01Tell it what I needKeep the request and useful context together

02Pick the right toolUse my iPad, Mac, or an online service

03Get the work startedSearch, build, check, or keep track of something

04See what happenedKnow what worked and what needs my attention

A few ground rules

What matters to me

These matter as much as getting something to work.

Finish useful things

I’m interested in results I can show and use, not big claims about what might be possible.

Get the facts right

Research should be traceable, and uncertainty should be called out.

Keep approval where it belongs

I stay in control of account access, payments, and sensitive personal decisions.

Spend carefully

Start with the devices and free resources I have; make costs clear before anything changes.

Game developer collaborations

Let’s bring more games to Apple devices.

I’d like to work with game developers, studios, and rights holders on Mac, iPad, and iPhone versions. I’m building a portfolio of feasibility studies and prototypes, with attention to local performance, graphics, controls, audio, and saves.

A useful starting point is one game, a target device, and a playable milestone. From there, we can assess the engine and dependencies, test on real hardware, and decide what a supported release would take. Official ports and distribution would be developed with the rights holder’s permission.

Email works best. Tell me about the game, its engine, existing platforms, and where you’d like to bring it next.

Discuss a Mac or iOS game port Explore a playable prototype Discuss touch controls and performance Offer developer tools or test hardware Apple’s game porting resources