An academic platform where a student’s question becomes a project with named roles and people who fill them. The funnel is the product. No skipping.
Someone gave the right answer three months ago. Nobody finds it. Every year starts over on the same questions.
A board. A shared folder. Cut off from the discussion that produced them. Six months later nobody knows why that task existed.
The project ends. Someone hands in the report, and the file stays on their drive. Next year someone else meets the same problem, never knowing it was solved.
LECO closes the loop. The question, the discussion, the work, the result. Then the result becomes a public resource the next one will find.
This is the only place on this page where you see the product.
A post tied to one to five topics and to one or more courses. You cannot publish without saying what it is about. The asker picks the best answer. One. A switch, not a vote count.
Zero pivot at (2,2). Is partial pivoting enough, or is another method needed?
Partial pivoting is enough here. The matrix is invertible — the failure comes from row order, not conditioning.
A. NdioneSame case in lab 4. The counter-example is in the resource linked to the project.
M. TraoréEdited twice — public history, not deletable
The public Q&A stays public. Alongside it, the group keeps internal conversations, attached to the project or to a work item. Fifteen minutes to fix a message. After that, or once the discussion resolves, it’s closed.
Do we keep both methods in the atlas, or only the one from the course?
Both. The second explains why the first one fails.
Two methods, one notation. To carry into the output.
Six item types and four states, seen three ways. The blocked state cannot be declared. It gets computed, from whatever blocks it.
ID98B-5 is blocked by ID98B-3 — the state is computed, never typed in
Draft, in review, approved, published. No public artefact skips review. And once it’s published, it becomes a resource the next ones will find.
Once published, the output returns to the public Q&A as a reusable resource
This is the shape of the product. The interface only follows it.
A public post tied to one to five mandatory topics and to one or more courses.
It declares a goal, an expected result, and the open roles with how many people each one needs.
It is a declared commitment to do one thing. Named, in one role, and accepted by someone.
When the conditions are met, the proposal becomes a private workspace for the committed group.
Nine kinds of output. Report, paper draft, comparison table, dataset, prototype, bibliography, synthesis, presentation, open resource.
If someone withdraws, the condition breaks and the proposal steps back down. You cannot fake being ready.
“This funnel exists to avoid empty projects. Users cannot create a complete project with one click.”
The create menu has two entries. No “create project” button. The column tying a project to its proposal is mandatory, and no endpoint creates a project.
An enforced hierarchy, and three views on the same data. Never copies.
A tree table, editable inline. The hierarchy is enforced. A subtask never floats alone.
Columns by state. ID98B-9 crosses the states one by one, leaving its empty slot behind.
Bars and dependencies. ID98B-5 starts after ID98B-3, because it depends on it.
Editable inline. Item numbers are never reused, not even after a deletion.
Task and bug under a story or an epic. Feature and story under an epic only. Subtask requires a parent, an epic has none. An item with children can no longer change type.
Two links: blocks and relates to. The blocked state follows from them. The graph detects cycles on every change and refuses the one that would create one.
32 permissions across seven areas compose reusable role templates. Asking to transition an item automatically adds reading it and reaching the workspace. An incoherent role does not get built.
A public question. An internal discussion. A decision note. A work item. You read them in a row, not in four tools.
The group asks the rest of the platform, choosing how much context to show: the project link, the topic only, or nothing.
Attached to the project or to a work item. Never to anything else. And once the discussion resolves, it closes.
An answer from the public Q&A can become a project resource. An answer written for someone else ends up in your project.
The public Q&A, flat: one question, one to N answers.
The group’s own conversations, which it can close.
Items and their states. What blocks what.
Status posts on the project timeline. Public or internal, always approved.
The deliverables and their review.
Links, files, notes — or an answer reused by the project.
This is where work becomes knowledge again.
The state turns to done. Reopening stays possible, if you say so.
A decision note. Two lines, attached to the work it explains.
Followers get whatever the project broadcasts.
Reviewed, then published. The resource for whoever comes next.
First name, last name, bio, university, department, academic level. The profile is public, on the open web. No anonymous mode, ever.
01 — 06
Three primary audiences, three secondary.
Ask the question from the course, and watch it become shared work.
Open a lead and declare the missing roles. The group forms itself.
The cohort is looking for something. Here you see it.
Structure collective work without leaving the discussion that started it.
A review thread becomes a reviewed, published deliverable.
Turn a cohort into projects whose trace stays.
“The asker knows their question better than random voters.” Instead, one best answer, picked by whoever asked.
“Flat Q&A: a question has one to N answers, full stop.” Answers can answer each other. There is no comment entity.
“LECO is an educational community with real identity.” The profile is a portfolio of public contributions. Courses followed and contributor projects only appear there if you switch them on.
Passkey or magic link by email. Nothing else to remember, nothing else to lose.
Opening the link does not consume the token: an explicit confirmation is required. It is a defence against mailbox security scanners. They would burn the link just by opening it. Fifteen minutes, single use.
A name, an email, and that’s it.
Nothing gets read outside its context.
A rule counts when breaking it is impossible.
The result becomes public again.
The asker decides.
Identity is real.
Attention is asked for.
Bring a workflow you’re in the middle of. A question, a discussion, work that has to end as a shared result.
A course, a topic, and a question you would ask today.
A place to ask it when your cohort opens. No date announced.
Just a name and an email. No password, ever. How this data is handled
The button opens your email app with your request. Nothing is sent from this page.
An academic platform. A student’s question becomes a proposal, then a project, then a public output.
Students, researchers and teachers. And the groups that make shared work out of a discussion.
No. Early access, not public yet, and no launch date.
LECO connects what they separate. The question, the work, the result, in one loop. And nothing imports itself automatically.
French as the main language, English and Italian from day one.