Thread to test a bit. Playing with the cpi's features. Not too much named as such, honestly! Keep on playing here, coding what's useful but no one can pay for. Would be too expensive anyway, *gg*.

note :/! a 'test' thread/story for quirling round with new cpi features.

Test Specification:
* systematic chosen: chaos force procedure.
* data: text and different (trees).
* documents: here and then.
* threads: $this one first, others come later.
* comments: subject of being automated, must work.

Assertions:
* some will fail, others won't.
* majority must be working.
* threads exist.

Sets:
* will be listed. when details aware.

Units:
- Update/Edit existing Thread.
doc :/!_ not within here. but maybe log com#s will appear.
- Create new Comment.
doc :/!_ by T(est)C(ase)#s most probably ordered best.
obj := unknown, various, or lots of. much of them, until uncountable.
- Create new Recomment.
doc :/!_ comments hanged in as childnodes of existing comments.
doc :/!_ requires different handling in terms of feature management, or just: dev.
- Upload.
doc :/!_ Files like Images, Printable Reports and the like must be uploaded by one of those modern, some call 'em nasty, web interfaces, terrifying users of the pro kind. That must be stopped! We as them are completely pissed of user interfaces restricting our functionality. No matter if driven by windows or operating systems.

Cases:
1) Storys, called Threads here.
2) Comments and Subcomments, Chapters and Sections internally.
3) File upload, image upload.

Objective:
a) test driven improvement of the C³PI "Early Core".
b) giving a demonstration of web publishing in modern ways.

End: unknown.