Demo Dashboard + ubiquity-os-simulant
#150
Comments
0x4007
added
Priority: 4 (Urgent)
Priority: 5 (Emergency)
and removed
Priority: 4 (Urgent)
labels
@gentlementlegen @whilefoo rfc on the
|
0x4007
changed the title
ubiquity-os-simulant[bot]ubiquity-os-simulant
|
I'm not sure if I understand how it's supposed to work. Is demo trying to replicate an existing issue in "realtime" or is the simultant executing actions based on what you choose in the "Demo UI"?
Maybe we can create a repo specifically for all demo issues and modify the vector embeddings plugins to exclude that repo.
This two steps wouldn't need to be done, if we have a repo for demo issues that's already set up.
I'm not sure what you mean by "inside the simulant", but I imagine we would have a server/worker that listens to requests from Demo UI and executes a scenario with fake user's PAT token? If we use Github Actions then the workflow would need to be stored somewhere where the fake user's token has permission to trigger it. |
|
I think it would be safer to make people try this in a new repo. We talked a bit about it already, but we noticed that most of our potential partners were using closed-source. Having the bot installed and running on their repo would require already high elevations (admin permissions for org and such) which can be a blocker for closed-source organizations. For the rest, instead of having a bot doing the actions, why not doing a tutorial and directly tell the user to do the actions? I am thinking like a |
|
To make my position clear: I'm mostly concerned with implementing this fast so for architecture and such details we can take shortcuts that we see fit.
This. It would be a choreographed typical set of actions. I also imagine it would comment some helpful tips for the user to read to better understand what is happening. Imagine if we were demonstrating the product to somebody in person or on a zoom call. We would be performing these actions as a user while explaining the context of those actions and why there is business value in the reactions of UbiquityOS
Sort of. You pick which "dance" it should do. Each "dance" is a set of actions to show off any specific capability of any specific plugin.
This was unintentional I actually made it quickly by finding and replacing Whilefoo in an old task.
We can solve this in a future task!
It would be an optimal demo experience if they had full GitHub UI and administrative control. They can open a new issue and repeat the steps exactly as the stimulant did (including adding labels!) to truly understand how to use the system. I guess we could dual purpose this as a tutorial mode as well.
Poor choice of words then
Yes that's correct. We can make the PAT inside a secret somewhere so we just need a way to run the GitHub actions from the Demo UI
Yes we can host it under the @ubiquity-os org as some new repo for tutorials/demos. |
This comment has been minimized.
This comment has been minimized.
|
@gentlementlegen I wrote a tutorial flow and realized that my simulant approach, which performs all the actions automatically and pretends to be a team member, would be more appropriate for this demo. Your bot approach would be more appropriate for a tutorial mode, which is more focused on educating the user on how to really use the system. This is prone to confusion and errors. There are also unsexy steps like having to initialize the special labels and registering a wallet before diving in. |
|
Then if there is no interaction at all, why not simply make a video (with a proper montage, captions and everything) which requires no installation at all? I don't see the point of having to install everything if it is for a demo tbh, 30 seconds video would be more efficient. |
|
We have videos but this gets them to install it and play with it. It's the natural next step in our business development strategy. @minhyeong112 rfc |
|
But they can't play with it since we simulate everything, and as you said
So either we bypass that problem and they can fully interact with the bot despite not setting up this, and the demo bot seems more relevant, either they don't and they can't interact so the video makes more sense to me in such case. |
No they can file a new issue very easily from the top right corner of the screen. The simulant scripts are invoked from the ui we build. They would do everything including creating a new issue for itself. In addition the user can interact with the closed issue at the end by trying some bot commands. |
technical details aside for a moment, I think the basic idea is something like this: https://www.photoprism.app/ I know this has nothing to do with UbiquityOS, but rather than them explaining things, if you click on "try our demo", you're instantly in an initialized demo where you can interact with their tool we would probably need a mixture of this, and a bit of a "tutorial" piece that tells people what to do |
|
We should get started on this now. @ubiquity-os-simulant is ready to go. I need an answer on using a modified kernel.
I can work on the UI now.
@gentlementlegen or @whilefoo should set up a new kernel or figure that out
@gentlementlegen or @whilefoo should make a plugin that follows a simple script |
|
@0x4007 Do you think a UI is needed for this? The user would still have to install the How about this: We create a Only thing that needs to be changed in the kernel is to react to |
Yes we use hyperlinks to guide the user to install. Its not complicated. I can handle that personally anyways, I just need a kernel endpoint to hit from the UI thats all. I think its very simple actually. If we fork the kernel and do a special worker for this. We can consider consolidating /demo into the kernel (similar to /help) as well but I feel like that is prone to more edge case problems then just doing a one-off kernel fork for this project. Given the time constraints I think we should go for simpler.
Sounds fine but to make myself super clear, make the hard coded configuration and commit to the repository config. Which is what I described in my comments earlier. Anything else like some type of internal only config would not allow the user to use the plugins normally like |
|
With what I suggest we could disable these plugins entirely or putting empty wallets and disabling comment evaluation etc as we see fit, and the user testing would not be able to override these. |
|
I want to demo daemon-pricing, task matchmaking, /ask, payouts. |
|
So if we do Then in the UI we can instruct the user to create a new repo, new issue, and then write |
|
I have to thoroughly evaluate all the aspects but it seems so far to be the simplest route to achieve a demo that is entirely scripted while using our real plugins |
|
Then lets do that |
|
/ask summarize a list of deliverables i need to hit in the context of building the ui |
|
Based on the chat history, here are the key deliverables for building the UI:
The focus should be on creating a simple, guided experience that demonstrates UbiquityOS's core capabilities while minimizing potential points of confusion for users. |
|
/ask list all the "Add helpful tips/explanations during demo flow" that I should include |
|
Based on the chat history, here are the helpful tips/explanations that should be included during the demo flow:
These tips should be integrated naturally into the demo flow to help users understand the system's capabilities and proper usage. |
|
/start @gentlementlegen |
Tip
|
Just realized we need to display both of our wallets probably. |
|
@minhyeong112 @v4d33m some quick updates on the demo but gentlementlegen built a plugin that controls a user profile @ubiquity-os-simulant and it steps through all the main set of actions a collaborator would take, live in front of the viewer. Meniole/.ubiquity-os#8 You can try by creating a new issue and writing /demo https://github.com/Meniole/plugin-demo/issues/new I'm wrapping up the UI to set it up. We can have a docs page with miguel's tutorial videos1, and then a link to "TRY THE DEMO" to my UI.
The vision is to invoke it from the UI, and then you click the link to watch the demo unfold in front of you. The user profile essentially is a simulated human team member. I expect this to be stable by Consensus HK Footnotes
|
|
love where this is all headed
So I'm using the paid "loom" subscription which should cover the hosting part. |
|
/ask when my ui generates the configured repository, it also creates a new demo issue as the user and displays a link for the user to navigate to the github issue. the issue body is the following, which is the user's first thing they will read. we need them to write /demo in order to have a team member simulate going through all of the normal motions of solving a task, like commenting /start to self assign, and linking a pull request and such. @ubiquity-os-simulant is summoned and starts working right away to show the users the features. in addition to performing the acitions it must to show off the system's features, it also will add commentary explaining the context of its actions and the expected reactions from our system and why they provide you business value. i want to know what the best issue specification would be to write given all of this context. you can use my existing one as reference but we want to make this feel high tech and futuristic, while also being concise and informative. |
|
Based on the context, I'll craft a more engaging and futuristic-feeling issue specification that introduces UbiquityOS while maintaining professionalism and clarity: 🚀 Welcome to Your UbiquityOS Demo Experience
Experience the future of decentralized collaboration firsthand. This interactive demo will showcase how UbiquityOS streamlines development workflows and automates task management.
### What to Expect
- Watch AI-powered task matching in action
- See automated reward calculations
- Experience real-time collaboration features
- Observe smart contract integration for payments
### Start Your Demo
Simply comment `/demo` below to initiate an interactive demonstration. Our AI team member @ubiquity-os-simulant will guide you through the core features while explaining their business impact.
---
💡 Pro Tip: Feel free to interact with any of the commands you see during the demo to explore the system yourself!This specification:
The tone aims to balance excitement about the technology with clear, business-focused value propositions. |
|
Caution All linked pull requests must be closed to generate rewards. |
|
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Task | 0.5 | 500 |
| Issue | Specification | 1 | 314.25 |
| Issue | Comment | 10 | 213.09 |
| Review | Comment | 2 | 2.34 |
Conversation Incentives
| Comment | Formatting | Relevance | Priority | Reward |
|---|---|---|---|---|
### Mockup ![Image](https://github.com/user-attachments/assets/… | 48.78content:
content:
h3:
score: 1
elementCount: 5
p:
score: 0
elementCount: 2
img:
score: 5
elementCount: 1
ol:
score: 0
elementCount: 1
li:
score: 0.5
elementCount: 15
ul:
score: 0
elementCount: 5
a:
score: 5
elementCount: 3
result: 32.5
regex:
wordCount: 400
wordValue: 0.1
result: 16.28
| 1 | 5 | 314.25 |
@gentlementlegen @whilefoo rfc on the `ubiquity-os-simulant&… | 5.32content:
content:
p:
score: 0
elementCount: 1
ul:
score: 0
elementCount: 1
li:
score: 0.5
elementCount: 2
result: 1
regex:
wordCount: 84
wordValue: 0.1
result: 4.32
| 0.8 | 5 | 27.2 |
To make my position clear: I'm mostly concerned with implementin… | 11.14content:
content:
p:
score: 0
elementCount: 1
br:
score: 0
elementCount: 3
result: 0
regex:
wordCount: 256
wordValue: 0.1
result: 11.14
| 1 | 5 | 71.45 |
@gentlementlegen I wrote a tutorial flow and realized that my si… | 4.32content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 84
wordValue: 0.1
result: 4.32
| 0.9 | 5 | 24.615 |
We have videos but this gets them to install it and play with it… | 1.65content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 27
wordValue: 0.1
result: 1.65
| 0.7 | 5 | 7.28 |
No they can file a new issue very easily from the top right corn… | 3.06content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 56
wordValue: 0.1
result: 3.06
| 0.8 | 5 | 15.48 |
We should get started on this now. @ubiquity-os-simulant is read… | 3.02content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 55
wordValue: 0.1
result: 3.02
| 0.9 | 5 | 17.325 |
Yes we use hyperlinks to guide the user to install. Its not comp… | 7.31content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 156
wordValue: 0.1
result: 7.31
| 0.8 | 5 | 37.04 |
I want to demo daemon-pricing, task matchmaking, /ask, payouts. | 0.71content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 10
wordValue: 0.1
result: 0.71
| 0.6 | 5 | 2.76 |
So if we do `/demo` and we make a new plugin, we don't n… | 2.1content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 36
wordValue: 0.1
result: 2.1
| 0.7 | 5 | 8.89 |
Then lets do that | 0.32content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 4
wordValue: 0.1
result: 0.32
| 0.5 | 5 | 1.05 |
Seems fine just some tweaks mentioned in my review. | 0.65content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 9
wordValue: 0.1
result: 0.65
| 0.6 | 5 | 2.34 |
Edited | 0content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 1
wordValue: 0
result: 0
| 0.2 | 5 | 0 |
[ 623.17 WXDAI ]
@gentlementlegen
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Task | 0.5 | 500 |
| Issue | Comment | 6 | 123.17 |
Conversation Incentives
| Comment | Formatting | Relevance | Priority | Reward |
|---|---|---|---|---|
I think it would be safer to make people try this in a new repo.… | 6.39content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 133
wordValue: 0.1
result: 6.39
| 0.9 | 5 | 36.855 |
Then if there is no interaction at all, why not simply make a vi… | 2.87content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 52
wordValue: 0.1
result: 2.87
| 0.7 | 5 | 12.915 |
But they can't play with it since we simulate everything, and as… | 3.29content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 61
wordValue: 0.1
result: 3.29
| 0.6 | 5 | 12.03 |
@0x4007 Do you think a UI is needed for this? The user would sti… | 6.55content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 137
wordValue: 0.1
result: 6.55
| 1 | 5 | 40.95 |
With what I suggest we could disable these plugins entirely or p… | 2content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 34
wordValue: 0.1
result: 2
| 0.8 | 5 | 9.8 |
I have to thoroughly evaluate all the aspects but it seems so fa… | 1.85content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 31
wordValue: 0.1
result: 1.85
| 0.9 | 5 | 10.62 |
[ 48.25 WXDAI ]
@whilefoo
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Comment | 1 | 48.25 |
| Review | Comment | 1 | 0 |
Conversation Incentives
| Comment | Formatting | Relevance | Priority | Reward |
|---|---|---|---|---|
I'm not sure if I understand how it's supposed to work. Is demo … | 7.43content:
content:
p:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 159
wordValue: 0.1
result: 7.43
| 1 | 5 | 48.25 |
Same issue on my end, first I logged in with Github and then "St… | 6content:
content:
p:
score: 0
elementCount: 5
ul:
score: 0
elementCount: 1
li:
score: 0.5
elementCount: 2
a:
score: 5
elementCount: 1
result: 6
regex:
wordCount: 109
wordValue: 0
result: 0
| 0.8 | 5 | 0 |
[ 67.225 WXDAI ]
@minhyeong112
Contributions Overview
| View | Contribution | Count | Reward |
|---|---|---|---|
| Issue | Comment | 2 | 67.225 |
Conversation Incentives
| Comment | Formatting | Relevance | Priority | Reward |
|---|---|---|---|---|
technical details aside for a moment, I think the basic idea is … | 8.79content:
content:
p:
score: 0
elementCount: 1
a:
score: 5
elementCount: 1
result: 5
regex:
wordCount: 72
wordValue: 0.1
result: 3.79
| 1 | 5 | 57.1 |
love where this is all headed So I'm using the paid "loom" subs… | 3.29content:
content:
p:
score: 0
elementCount: 1
br:
score: 0
elementCount: 1
result: 0
regex:
wordCount: 61
wordValue: 0.1
result: 3.29
| 0.5 | 5 | 10.125 |
Mockup
Overview
We should have a "try demo" button on ubq.fi and this should bring the user to a "Start Demo UI" to be able to easily set up:
ubiquity-os[bot]- our production deployment..ubiquity-osrepository and push.ubiquity-os.config.ymlwith default settings (hardcoded evm wallet with no money should be fine.)The "try demo" dashboard should have buttons for each of these capabilities that trigger the @ubiquity-os-simulant to run choreographed scenarios to demonstrate each capability. It should basically pretend to be the user's knowledgeable team member.
Capabilities shortlist:
/askResearch Needed
Deliverables
/helpmenuNext Steps
Footnotes
Does it make sense to just file demo issues inside of the
.ubiquity-osrepository? ↩Or we can do separate typescript files/directories per demo, whatever makes more sense I'm not sure. But separate GitHub Actions may make changing any environment variables simpler. ↩
It needs to be able to load its own config most likely i.e.
.ubiquity-os-simulant.config.yml↩The text was updated successfully, but these errors were encountered: