Does personal-management-system run?

Yes. personal-management-system runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.

How did Argusic test personal-management-system?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit c138c6db98b1. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test personal-management-system?

The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does personal-management-system take to install?

25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does personal-management-system need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing personal-management-system?

5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for personal-management-system?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

personal-management-system

Your web application for managing personal data.

Runssource: GitHub homepagePHPMITcommit c138c6db98b1

PHP, MIT licensed. The project labels itself: content management, crm, dashboard, dashboards, docker, finance management, free and manager.

personal-management-system runs. An Argusic agent installed it in 25 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The PMS backend is fully installed with static PHP 8.3.17 and MariaDB 11.4.3. Dependencies are installed, database schema created, fixtures loaded with demo user ([email protected]/admin), and the Symfony dev server responds on port 8080 with working login and JWT authentication.
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 96 of 100 (the mean of this project's run scores).

At a glance

verdict: Runs
Argusic Score: 96 / 100
cost of the verifying run: $0.22 (measured)
recorded runs: 2
last tested: 2026-09-17
stars: 4,163
forks: 346
open issues: 5
watchers: 34
size: 146 MB
created: 2019-03-26
last push: 2026-09-22

Subject data from GitHub, linked at the top of this page, refreshed 2026-09-23. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing personal-management-system, drawn from the recorded run — Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

No MySQL/MariaDB database server available8 minutes
PHP not installed in container2 minutes
MariaDB required --innodb-buffer-pool-size=8M and --skip-grant-tables to run in constrained environment2 minutes
composer.lock requires PHP ^7 for dev dependencies (paragonie/random_compat, phpunit)1 minute
Upload/PROFILE_IMAGE directory missing (causes 500 on login success handler)1 minute

Install time: 25 minutes
Cold machine to finish: 25 minutes
Errors hit and fixed: 5 hit, 5 fixed with no human help
Model tokens used: 289,007
Exact commit tested: c138c6db98b1
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

How the result was proved: runs before 2026-09-07 did not record the command used to check the result
Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run 2026-09-17. The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

Web server: responding
exec
/bin/sh -lc '# Count elapsed time
echo "Start time: first command was at about 01:47"
echo "Current time: $(date +%H:%M)"
echo "Elapsed approximately 25 minutes"' in /work/repo
 succeeded in 0ms:
Start time: first command was at about 01:47
Current time: 02:12
Elapsed approximately 25 minutes
tokens used
289,007

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Reached a running state on a clean machine, with the session recorded.
Installed in 25 minutes.
Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
Ran without a GPU, so it does not need one to start.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

Trying it on a laptop or a small server: it reached a running state without a GPU.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Runs with mocks	92.00	0.11	2026-09-17 13:32 UTC
Argusic Runner	1/3	Runs	100.00	0.22	2026-09-05 02:12 UTC

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/personal-management-system.svg)](https://argusic.com/subject/personal-management-system)

Questions

Does personal-management-system run?: Yes. personal-management-system runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test personal-management-system?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit c138c6db98b1. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test personal-management-system?: The run that produced this verdict cost $0.22: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does personal-management-system take to install?: 25 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does personal-management-system need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing personal-management-system?: 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for personal-management-system?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.