Carbon felt
| Property | Value |
|---|---|
| Porosity | 0.93 |
| Tortuosity | 1.8 |
| Specific surface | 30,000m²/m³ |
| Permeability | 3.00e-10m² |
| Thickness | 5mm |
Turn on comment mode, click any value or card, and say what is wrong or what should change. The comment is pinned to that element and carries the entity behind it, so Claude knows which electrode, which property and which number you mean.
| Property | Value |
|---|---|
| Porosity | 0.93 |
| Tortuosity | 1.8 |
| Specific surface | 30,000m²/m³ |
| Permeability | 3.00e-10m² |
| Thickness | 5mm |
| Property | Value |
|---|---|
| Porosity | 0.78 |
| Tortuosity | 1.8 |
| Specific surface | 120,000m²/m³ |
| Permeability | 5.00e-12m² |
| Thickness | 190µm |
| Property | Value |
|---|---|
| Porosity | 0.45 |
| Tortuosity | 1.5 |
| Specific surface | 1,800m²/m³ |
| Permeability | 7.00e-9m² |
| Thickness | 50mm |
Each value on the page declares its data entity: which record, which field, the value shown, its source.
In comment mode a click reads that declaration, never the screen text, and opens a comment pinned to the element.
The comment and its entity context go to Claude, who answers about that exact value and proposes a fix with provenance.
Extend the existing page comments with anchor columns (entity kind, entity id, field, value at the time of the comment), so a review queue can filter by entity, then let pages opt in by marking their values.