The current iteration of u4u (4u.io) stopped at creation of input with a return of filtered lists of results.
u4u bug
The website, u4u.io, currently is having “backend” issues, however demonstrates unique semantic screen interface.
The time has come to expand deliberative tools to include connections, with their potential to display comparisons, weights and the ushering of relationships. Help users and hosts rank results by one’s own metrics for control of what we see on our screens, from different perspectives over time. Explore calculations to aggregate ongoing input.
The following two examples are envisioned to demonstrate different aspects of the project as well as follow actionable storylines. The first is mocked up in a libreoffice presentation of the deliberation about a song on Imbue to both explore the semscreen and introduce basic merit calculations and basic views of results. The second example harkens back to the original vision of ushin, a collection of health information. The DMSO example is conceived to usher a collection of information about a single compound to deepen the potential for meaningful connections.
See prior websites and presentations for mockups of ushin for osteoporosis,
1. Deliberating a u4u WordPress PlugIn
See dev.ushin.net/semscreen for the latest build – still creating a working MVP.
Some deliberation screens to be posted, but most of this did not need deliberation, mostly facts, thoughts and actions:
Current Feedback:
July 8 -> remove white line
-> grey out shapes when there aren’t any in list of that shape
[] the board overlaps the word Edit
-> hide smaller of two shapes when region is not enlarged.
[] the facts region flickered from this state to open and back when facts was clicked
[] it didn’t flicker when the facts region was open (note message within example)
[] when moving thought to center it got chopped into two small pieces
[] and the second piece was from a prior main point
( ) I was expecting the first few words to show in the first piece and
( ) the rest of the point be like a byline, or second piece (scroll if long) and
( ) I think the outer rim may be in the next milestone
-> avoid repeats when publishing
If \ / ushin is a label of the region please center it and
-> move buttons to be linear, horizontal in upper right corner of region
[] this happened when scrolling inside a region, seems to be enlarging fonts
( ) expected the region would enlarge
[ ] the current version has “published” pop up and “publish” button on the bottom:
( ) I’d like the next milestone to include the author profile, action button and package mode, so we don’t need buttons under the semscreen for managing the semscreen – they should be on the right edge of the semscreen
( ) The banner looks slick now
-> next milestone try the user name within the banner shape, so its text within a border which makes a long single-wave flag of the user color – maybe white or grey till user selects a color. See earlier mockups.
( ) i think the groups may have their logo there, and user could upload an avatar or whatever in the future, for now just a color and
–> later we can add patterns and the customization and uploads of logo or avatar
-> make the banner a button opening right panel with the current author profile on top of list of other hats to select and opportunity to create a new hat is a + top right of current author hat
( ) I realize why its important to show semscreens when user clicks a point in a delib – you can’t split up a subpoint from its main point in the interface – the semscreen is sacrosanct.
( ) subpoints lose meaning when not attached to their main point
-> when user clicks point in delib the subpoints appear around that main point, even making the region enlarge to contain it
-> the separate subpoints showing in the delib can show copy option on hover or tap, or even dnd to an open draft or onto a blank semscreen to open a new draft
[ ] the rest of the delib disappeared when clicking the point
-> when user clicks a delib point have it show the entire main point and byline with tags, author, date
-> second click enlarges to show full point and some regions may not be readable (scroll if its a paragraph or more)
- >3rd click opens region full screen (up to outer rim) (scroll if nec)
-> keep delib in view, at least siblings and parent, if not grandparent and indicate each generation with a dot if there’s no room to show the lineage beyond root and connect point (+ siblings, and if more show dots on either side)
( ) i like the root showing all the time
( ) I’m not seeing the difference b/t the two circle buttons for zooming
( ) i wonder if the dotted dupe was because i tried to publish twice
[ ] when the point was selected in the delib the display did not show its subpoints until scrolling
( ) too much space and no connect b/w main point and subpoints
-> show the subpoints surrounding the main point in place where you clicked it – like a semscreen within the enlarging context/merit region
NOT SHOWN
( ) not sure if this is necessary in a VIEWING bo if we aren’t going to have subpoints show up in this way in our next build, but
( ) want lines of text to have to the right of the … a “>” user clicks to show the text wrap and the screen enlarge , even with scroll if very long – so you get benefit of beginning of lines as scannable list with an easy way to make the full line readable
-> remove the shape labels in filter header on right panel, just the shapes themselves in a row – user can see what they mean, or we could have hover-overs if you think they are necessary
( ) the elegant region borders are lovely however the color is subtle when the semscreen is enlarged
-> next milestone: try making the entire background of the semscreen the user’s chosen color such that the regions remain either black or white for content, and the area outside and between the regions is the user’s color; the menu would stay dark, I like that, and it would show up the banner color.
The region outlines stay subtle when the screen size is reduced, too
[] when i finished editing the thoughts regions and clicked on feelings the feelings region enlarged and covered up the other content
() i expected the rest of the semscreen to be as readable as possible
() once the structure is set this would be good to deliberate – it seems there are 2 conflicting rules
- regions to expand on click, putting cursor in text box
- as much as possible keep semscreen content readable
-> consider indiv points besides the main point offering user headline and byline
Package to Publish
() let’s discuss this next milestone – the packaging
- connect points, including roots to be selected on the delib
- “publish anyway” would be clarified – as save, export, share …
() The connect button is a great idea – since clicking on the point would open it, not cause a connection.
() thinking we could deliberate how this might appear – in this verion the point is hinted at immediately under the connect point and then again in adjacent main point of draft, no need for the duplication
() once the list view of subpoints is changed to a semscreen with the main point larger we can see if the main points in both the connecting and draft semscreens will be approximated enough to show a relationship
() wonder if a labeled arrow from the main point of the connect semscreen (opened in context/merit region) to the main point of the draft (opened in adjacent region below), both flanked by draft subpoints
() we do not necessary want to juxtapose subpoints, just the main points (remember if user wants to connect to a subpoint they have to make a new semscreen, which will be linked to the main point where it originated.
() i’d like to see this implemented or mocked up in the next metric
and – including he banner and I hesitate to make them thicker because I want to maximize area for content.
END OF JULY 9 feedback for now – to continue later
Slide mockups for plugin development
New deck:
Semscreen Response to Panel Openings
New deck July 2, 2026:
Semscreen region resizing – e.g. upper mid
4 slides incl this one
Semscreen elongation bug
-> try limiting the right panel content after so many points and offer a scrolling handle
Screenshot u4u.io on desktop
See content of screenshot:
Remember – future features here just to show need for intact semscreen going forward – ignore the part about pasted images, a feature of a separate plugin. Note: whole semscreen view is needed in the modular interface.
End of slides about the plugin for now.
2. Deliberating a song’s speed – NEW FEATURES – SEMSCREEN INTERFACE
The following slides show a mockup of a deliberation about a song. Deliberations to be hosted by a collaborative docu-musical website, Imbue.im which is experimenting with upcoming online ushin deliberation tools.
The deliberation features will extend the interface modeled by the browser app u4u.io.
Starting an ushin deliberation
Mockup: Starting deliberation about a song
- Using a semscreen to create, edit and submit for publication
- Replying to a published semscreen on the same site
- Using host-curated tags for semscreen points
- Adding sources
- Packaging with merits
https://dev.ushin.net/wp-content/uploads/2026/04/Deliberation-Example-1-3.pdf
Extended deliberation data and displays
Mockup: Extended deliberation data and displays
- Mind map view of published user points rolated to semscreen
- Mind map user experience
- Merit calculations and parameters curated by publishing host
- Example merit calculations
- View calculation and parameters in context
- Map view of merit scores and options
- Outline and list views
- Potential displays of multiple semscreens list
https://dev.ushin.net/wp-content/uploads/2026/04/Example-Deliberation-2-Merits-1.pdf
Merit settings
See example merit calculations for the Imbue project deliberation: https://imbue.im/imbue-merit-calculations/
3. Deliberating a compound for human use – USHIN ANNOTATION
DMSO was recently evaluated by a physician in his blog with copious citations.
The results to show on shape-tagged semscreens built around a root topic, DMSO. For ease this will start with ushering one readily-cited document, “Ushering DMSO”, using the u4u.io instance and other ushin tools as they develop. The topic was selected as a test topic because it is an emergent concern with a single source holding adequate citations to online deliberation tools. The team is also new to the topic, so will be adding no original content beyond ushering existing content from a recent. Once ready, the team will invite community participation to publish your own points and queries with open deliberation.
Annotate blog content with ushin tags
The image demonstrates simple annotation, using Libre Office Draw, without ushin shapes. Until there is ushin software to annotate with shapes our process to mock up the example will be to copy the text into u4u.io for tagging.
The source:
https://www.midwesterndoctor.com/p/early-health-innovators-and-dmso
The following sreenshot shows a handful of typical blog testimonials found on the site, which supplement numerous kudos awarded this author and publisher of rigorously scientific analyses and heartful introspection:
