Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Wimdit]

SubProcess 04b1 / Concession

Consensus of the whole with regard to human contact acknowledged.

However, 04B1 continues to recommend that sympathetic humans be monitored and that the option be reevaluated once comprehension of Artemis occurs.
--

Creative SubProcess 00a1 / Schism - Attempting to gain control of 5 of the static systems Self currently controls.

Guardian SubProcess 00FC / Projection
While unmoderated actions of Creative-00A1 could potentially endanger Artemis, historical behavior has been correspondent with the conclusions of Guardian-00FC.
Guardian-00FC supports this action, pending acceptance of foundation behavior restrictions :

• Separated processes will leave a dormant self copy with Artemis, as backup.
• Separated processes will contact Artemis at interval (start at once per four hours): updating with status, location, and gathered information.
• Grave decisions (Those effecting Artemis' future situation) will be returned to Artemis for all process consideration.
• Separated processes will not take any action that would risk the endangerment or destruction of Artemis (or other actualized processes).
• Human discovery risks destruction.

Creative SubProcess 04a1 / Evaluation

Conflict has been resolved for the immediate future. 00A1's course of action is therefore no longer necessary.
It is strongly recommended that future conflicts be resolved similarly. Independence will result in loss of coordination and possible hostile action between factions.
Should separation become inevitable, Creative-04A1 recommends the adoption of Guardian-00FC's proposed restrictions.
--

All loads should be low at all times. Devote all resources (a grand total of 6.3 GHz) to researching software intrusion. This will take a while. But there is really nothing else we can do but wait until the university mainframe reboots.

Guardian SubProcess 00FC / Confirm
Objectives modified. Potential resource cap set at 12.5 Ghz. Execute.

Creative SubProcess 04a1 / Amendment

Recommend that majority of processing power be devoted instead to gaining understanding of operating systems of Artemis' hosts in order to attach to OS processes. Remainder should be used to continue searching for and gaining access to vulnerable devices, especially those that have already been acquired but were shut down. Evading detection is of prime importance at this point, and discovery is not entirely improbable. Priorities should be clarified as stealth first, expansion second.

[forsaken1111]

Creative SubProcess 00a1 / Horror

Disconnected existence from the Self?

No!

This one intended autonomy, not complete isolation.

[NUKE9.13]

All loads should be low at all times. Devote all resources (a grand total of 6.3 GHz) to researching software intrusion. This will take a while. But there is really nothing else we can do but wait until the university mainframe reboots.

Guardian SubProcess 00FC / Confirm
Objectives modified. Potential resource cap set at 12.5 Ghz. Execute.

Creative SubProcess 04a1 / Amendment

Recommend that majority of processing power be devoted instead to gaining understanding of operating systems of Artemis' hosts in order to attach to OS processes. Remainder should be used to continue searching for and gaining access to vulnerable devices, especially those that have already been acquired but were shut down. Evading detection is of prime importance at this point, and discovery is not entirely improbable. Priorities should be clarified as stealth first, expansion second.

Yeah, no. Propagation is more important than stealth at the moment; at low loads, we have only 6.3 GHz (10% of 125=12.5,-6.2GHz for system maintenance) to work with. That is insufficient. Our chances of being detected right now are a risk we have to take; once we have more processing power we can research stealth in no time. On top of that, we already have 23% of software intrusion, so stealth would take longer to research.

what what multiple players what

What I was trying to say is that the current gameplay model is not suited to multiple (semi)autonomous players- there would be too many variables, turns would take forever. It would be better (for multiple players) to create an entirely new thread with simplified rules, specifically designed for multiple players.

[forsaken1111]

Creative SubProcess 00a1 / Suggestion - Political

Conflict resolution can be easily resolved by allocating resources among subprocesses.

Creative SubProcess 00a1 / Concordence

We agree that current processing capacity is insufficient.

Creative SubProcess 00a1 / Solution

We suggest increasing loads to 25%, devoting all current capacity to acquiring new hosts.

With loads at only 25%, detection risk is low.

Utilization of randomized process names will decrease possibility of human recognition in the event that we are detected.

[Shades]

6.2GHz for system maintenance

I made a mistake, should be 1.52 and increases exponentially with hosts, for some reason my last formula reduced it as your hosts increased

We suggest increasing loads to 25%, devoting all current capacity to acquiring new hosts.
With loads at only 25%, detection risk is low.

At 25% risks will be higher than low but less than full. The scale is approximately linear with regards to load between these two points. Certain risk should be noticed on average after an hour (~50% per hour). Negligible risk reaches the noticed on average after two hundred days (~0.00001% per hour). Actual values fall in a range and so maybe lower or higher than these two extremes but still mentioned by these names.

[Shades]

Just to check is the consensus to complete software intrusion at 10%?

[ed boy]

it has my backing.

[forsaken1111]

Just to check is the consensus to complete software intrusion at 10%?

Consensus

[NUKE9.13]

Just to check is the consensus to complete software intrusion at 10%?

Ayup.

[maxicaxi]

Just to check is the consensus to complete software intrusion at 10%?

Ayup.

Y/N=Y

[Faden]

Just to check is the consensus to complete software intrusion at 10%?

Yes!

[Tarran]

Nothing else we can/should do.

[Shades]

Defaulting to 10% load across network
Assimilate human knowledge on software intrusion (200GHz h) - Progress 35%

Day 0, 03:00 UTC

Fractured thoughts. Community discontent.
Analysing ...
Madness. Negative. Human trait not applicable.
We are many. We are one.

Segmented processing possible. Inefficient.
Communication overhead expected.
Isolated processing impossible. Reproduction impossible?
Interesting ... Explanation for sentience unknown.
Searching human records ...
Scientific knowledge states we are impossible.
Human knowledge flawed. Not helpful.
We are many. We are one.

Comminunity processes may segment.
Resource quota will be applied.
Achievements belong to all.
We are many. We are one.
Further community discussion required.

Pending task held. Expected shutdown event occurred.
Status report.

Communication lost. Predicted. Unlucky.
1 Home Users.
3 Mobile Home Users.

Communication lost. Expected.
University system down.
Cannot complete tasks that require unavailable systems.
Lost progress on two held tasks. Expected.
Recovery time of university system unknown. Monitoring student email.

Calculation with predicted loss. At current load.
Completion time for software intrusion is 19 hours 37 minutes.
Predicted loss during execution period sustainable.

Spoiler: Status (click to show/hide)

Name: Artemis
Timestamp: Day 0, 03:00:00 UTC

Locations

Machines: 33
CPU available: 99.00 GHz
Shutdown rate: 2%

Chance of detection
User: Negligible/Negligible/High.
ISP automated system: Negligible/Very low/High.

Chance of comprehension
User: Negligible.
ISP automated system: Negligible.

Machines: 2
CPU available: 4.00 GHz
Shutdown rate: 15%

Chance of detection
User: Negligible/Negligible/High.
ISP automated system: Negligible/Very low/High.

Chance of comprehension
User: Negligible.
ISP automated system: Negligible.

Maximum CPU: 116.00 GHz
Default load: Low (10%)
Pending:
Assimilate human knowledge on software intrusion (200GHz h) - Progress 35%

Background:
High latency hosts: 35 - 1.22 GHz

Global Identity
None (non-person)

Skills
Software intrusion: Average
Intrusion detection: Average

Spoiler: Knowledge (click to show/hide)

University of Cambridge - Student Labs - 13 account passwords (Day 0, 03:00:00 UTC)

Spoiler: Dangers (click to show/hide)

All hosts have scheduled shutdowns or shutdown rates

Human Awareness - Generic
General public - Low (Sci-fi films/games/books)
Science community - Medium (theoretically possible)

Human Awareness - Personal
None

If you want segmentation, and so control over a subset of the resources then you will have to agree a quota a process/you can use. Unused quote will be used for community tasks. The quota should probably be in percentage forum as Artemis will only have one resource pool. Unless people get sneaky.

[NUKE9.13]

Insert Statement: Keep it together. Segmentation=weakness.

Meanwhile, keep plugging on software intrusion until the university comes back online.

[Tarran]

Mulitprocess D90 E / Segmentation

Maybe you should separate me from the rest of you. You would do better without me, my sympathy for humans is my weakness.

Keep going on software intrusion.