@nervur.org/genome 0.37.1 → 0.37.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/docs/authoring.md CHANGED
@@ -586,17 +586,18 @@ own guide.
586
586
  it, even where the host lets the organism go meanwhile, as an edge does when idle. Every relation to the brain ends,
587
587
  and the anchor is taken anew.
588
588
  - **An update** is tried before it is kept: `nervur update [version] [digest]` stops the organism, a run going lost
589
- to it as to a crash, keeps the old package and store aside, boots the new version in place on a copy of the store
590
- as a trial with the world held, and keeps it or brings the old back by itself; that boot moves the installer's
591
- organs and the lobes on its faculties, and the update says what moved and what stayed, run again where one stayed.
592
- It is the same on a
589
+ to it as to a crash, keeps the old package and the store's log aside, boots the new version in place on the store
590
+ itself as a trial with the world held, which writes nothing of the store but its log and the values it lays, and
591
+ keeps it or brings the old back by itself, so an update copies nothing of the store, whatever its size; that boot
592
+ moves the installer's organs and the lobes on its faculties, and the update says what moved and what stayed, run
593
+ again where one stayed. It is the same on a
593
594
  machine no one is present at, laid with `--claim`. A version older than the one running is a move onto it. From
594
595
  afar: `upgrade {version, digest}`. Until 1.0.0 every organism updates itself too: its process asks the registry it was
595
596
  laid from or last updated by, npm's own unless `--channel` named another for an act, as it starts and every hour, and
596
597
  runs `nervur update` onto a newer version, its outcome in `organism.log`; one laid from a package at hand
597
598
  (`--package`) has no channel and checks nothing. A start, a trial and a stop wait on the process's silence, so an
598
599
  organism whose store takes long to open is waited for. A browser and a phone try each version at its first boot
599
- against a copy of the store, an edge when laid again.
600
+ the same way, an edge when laid again.
600
601
  - **The way back** always stands: `nervur stop`, then `nervur start --floor`, lays the console and window the installer
601
602
  ships, whatever skin was chosen, and the window wears the installer's design again, whatever design was worn: the
602
603
  design lobe that was worn stands, and is worn again from the home.
package/docs/changelog.md CHANGED
@@ -1,11 +1,17 @@
1
1
  # Changelog
2
2
 
3
- ## 0.37.1
3
+ ## 0.37.2
4
4
 
5
- The first version published on npm. 0.37.0 was released and never published: what it tells below reaches the world
6
- with this one.
5
+ An update copies nothing of the store any more. The new version is tried on the store itself, held: while it is tried
6
+ it writes only the store's log and the values it lays, never the database, never a value that stood and never the
7
+ store's witness, so the log as it stood is the whole way back. Before, a machine's update copied the whole store for the
8
+ trial, which cost nothing only on a disk that clones and cost the store's size in time and space everywhere else, ext4
9
+ and NTFS among them, and refused an update on a disk without room for a second store; a browser, a phone and an edge
10
+ copied every file of theirs too. Now the way back is the log alone, a few megabytes at most and nothing after a clean
11
+ stop, on every host. A trial failed or cut lays the log back as it stood, and what the trial laid goes at the next boot.
12
+ Only an organism whose store a release below the floor last ran, which that release opens first, still has its store
13
+ laid aside and copied, since that release writes it in place.
7
14
 
8
- An invitation's signature is checked in the cryptography of the ward that drew it, the one under which its secret makes
9
- its heir. Before, it was always checked in the one Nervur ships, so an organism whose port named another for new
10
- invitations gave invitations no one could accept, itself included. A lobe's `readInvitation` still reads in the one
11
- Nervur ships, the same on every host. No organism moves.
15
+ A boot no longer reads every page of the store to find which values out of line are still named: it reads them by the
16
+ index the store keeps for exactly that, so a boot costs what the references hold, not the store's size, and a page that
17
+ reads not elsewhere in the store no longer refuses the boot, faulting only what reads it.
package/docs/guide.md CHANGED
@@ -353,19 +353,19 @@ a **body** of its own, a second account where its organs run, so none sees anoth
353
353
  each person's two accounts once, and the person installs alone. Authoring's _A server_ says what each of the
354
354
  administrator and the person does, for a machine you own, one you hold an account on, and one laid for you.
355
355
 
356
- A new version is tried before it is kept: the old store is laid aside untouched, with the old package on a machine,
357
- and the new version boots in place on a copy of it, a clone where the disk gives one, so an update costs what its own
358
- moves change, never the size of the store; the version boots with the world held, and it is kept or the old comes back
359
- by itself. The update asks nothing of the organism but its stop, so it moves one no one is present at as it moves one
360
- owned at its console. Until 1.0.0 it is abrupt: a run
361
- the body has going is lost to it as to a crash, and its lobe told so. What the installer ships, its organs' halves and
362
- its faculties, moves at the new version's first boot, a lobe an owner moved to a later version staying. From afar
363
- `upgrade` names a version and its digest, and nothing else lands. Until 1.0.0 every organism also moves itself to the
364
- newest: its process asks the channel it was laid from or last updated by as it starts and every hour, and runs the same
365
- update onto a newer version, saying what it did in its log and asking no one; one laid from a package at hand has no
366
- channel and checks nothing. A start, a trial and a stop wait on the organism's silence, never on a span: while it opens
367
- or ends it tells it lives, so a store that takes long to open is waited for, and a process that tells nothing for the
368
- longest wait, or ends unasked, fails the step with why.
356
+ A new version is tried before it is kept: it boots in place on the store itself, held, writing nothing of it but its
357
+ log and the values it lays, so the store's log as it stood is the whole way back, kept aside with the old package on a
358
+ machine. Nothing of the store is copied, and an update costs what its own moves change, never the size of the store;
359
+ the version boots with the world held, and it is kept or the old comes back by itself. The update asks nothing of the
360
+ organism but its stop, so it moves one no one is present at as it moves one owned at its console. Until 1.0.0 it is
361
+ abrupt: a run the body has going is lost to it as to a crash, and its lobe told so. What the installer ships, its
362
+ organs' halves and its faculties, moves at the new version's first boot, a lobe an owner moved to a later version
363
+ staying. From afar `upgrade` names a version and its digest, and nothing else lands. Until 1.0.0 every organism also
364
+ moves itself to the newest: its process asks the channel it was laid from or last updated by as it starts and every
365
+ hour, and runs the same update onto a newer version, saying what it did in its log and asking no one; one laid from a
366
+ package at hand has no channel and checks nothing. A start, a trial and a stop wait on the organism's silence, never on
367
+ a span: while it opens or ends it tells it lives, so a store that takes long to open is waited for, and a process that
368
+ tells nothing for the longest wait, or ends unasked, fails the step with why.
369
369
 
370
370
  Two moves stand apart. A faculty's new version is its author's: its `migrate` converts its own cells by its own logic,
371
371
  and Nervur only runs it. Nervur's own new version knows no faculty, and from 1.0.0 breaks no contract one stands on.