How it works / Concepts
Chat
“Do we store a ride's departure time?” takes ten seconds to ask and twenty minutes to answer. You have to find the right repository, then the right migration, then the person who wrote it, who is in a meeting.
A Chat is a private conversation between one member and Jigward, inside one Context.
What changes
-
Before: Pinging the backend engineer to ask which table holds a booking.
With Jigward: An answer from the schema the migrations build, with the files it read.
-
Before: A half-formed idea for meteor shower warnings.
With Jigward: A Task card worked out in the conversation, which only your click creates.
-
Before: “Can someone keep an eye on pull request 37?”
With Jigward: A Duty that looks every hour and reports back in the Chat.
-
Before: “Why did bookings to Moon Base 2 fail at 3 a.m.?”
With Jigward: The log lines it read, kept as a file, and what they do not say.
How it works
-
Ask in your own words
Jigward decides whether the question needs looking into. A simple one gets a simple answer.
-
It reads, and only reads
It can read the repository's code on its default branch, what it remembers, the Context's Tasks, public web pages, connected logs, custom integrations and Applications.
-
It shows what it read
Each file comes with the commit it was read at, and each page with its address. What it could not find, it says instead of making it up.
-
Work leaves as a Task
When something needs changing, Jigward proposes a Task card. Nothing but Create task starts it, and its report comes back to the Chat.
What it can do
-
Answer from the code
The schema, the API, how a feature works. It answers from the repository rather than from a guess.
-
Search the logs
A narrow search or a bounded query in the connected AWS accounts, with the lines kept as a file only you can open.
-
Propose a Task
It raises what the request leaves open, asks what only you can say, and then writes the card.
-
Come back later
When the conversation calls for it, Jigward gives a Duty and shows you its instruction and schedule.
-
Build an Application
A page, its data and the way it is filled, without leaving the conversation.
-
Find past work
“The Task that fixed the night fare, and its recording.” You get a link that opens that file on the Task.
How it connects
- Contexts A Chat belongs to the Context it started in, and switching Context never widens what it can reach.
- Tasks A Task it proposes is created only by your click, and reports back into the Chat.
- Duties It gives a Duty when the conversation calls for coming back to something.
- Applications It builds Applications, and the Chat on an application's page works on that application alone.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.